IBMTivoli OMEGAMON XE for IMS on z/OS Version 5.1€¦ · Chapter 1. Overview of configuration...

IBM Tivoli OMEGAMON XE for IMS on z/OSVersion 5.1.0

Parameter Reference

SC27-4430-00

��

IBM Tivoli OMEGAMON XE for IMS on z/OSVersion 5.1.0

Parameter Reference

SC27-4430-00

��

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

This edition applies to Version 5, Release 1, Modification 0 of IBM Tivoli OMEGAMON XE for IMS on z/OS(program number 5698-T02) and to all subsequent releases and modifications until otherwise indicated in neweditions.

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

Contents

Tables . . . . . . . . . . . . . . . v

Chapter 1. Overview of configurationparameters . . . . . . . . . . . . . 1Location of stored configuration parameters . . . . 1

Parameter names . . . . . . . . . . . . 2Parameters used by the PARMGEN configurationmethod . . . . . . . . . . . . . . . . 2Generating and editing the configuration profile . . 3Parameters in the Configuration Tool . . . . . . 4Parameters in batch mode processing . . . . . . 4Default values . . . . . . . . . . . . . . 4

Chapter 2. KI2 configuration parameters 7KI2_CLASSIC_STC_PREFIX . . . . . . . . . 10KI2_CLASSIC_UMAX . . . . . . . . . . . 11KI2_CLASSIC_VTAM_APPL_PREFIX . . . . . . 12KI2_CLASSIC_VTAM_NODE_PREFIX . . . . . 13KI2_CUA_STC . . . . . . . . . . . . . 14KI2_CUA_VTAM_APPL_CMD . . . . . . . . 15KI2_CUA_VTAM_APPL_I/CF . . . . . . . . 16KI2_CUA_VTAM_APPL_LOGON . . . . . . . 17KI2_CUA_VTAM_APPL_OPERATOR. . . . . . 18KI2_CUA_VTAM_APPL_PREFIX . . . . . . . 19KI2_CUA_VTAM_NODE . . . . . . . . . . 20KI2_CUA_VTAM_VTPOOL_NUM. . . . . . . 21KI2_CUA_VTAM_VTPOOL_PREFIX . . . . . . 22KI2_CUA_WTO_MSG . . . . . . . . . . . 23KI2_CLASSIC_STC_NUM . . . . . . . . . 24KI2_I1 . . . . . . . . . . . . . . . . 25KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR . . . . 26KI2_I1nn_CLASSIC_IMSID . . . . . . . . . 27KI2_I1nn_CLASSIC_IMS_RESLIB . . . . . . . 28KI2_I1nn_CLASSIC_LROWS. . . . . . . . . 29KI2_I1nn_CLASSIC_MPREFIX . . . . . . . . 30KI2_I1nn_CLASSIC_STC . . . . . . . . . . 31KI2_I1nn_CLASSIC_USER_PROFILE . . . . . . 32KI2_I1nn_CLASSIC_VTAM_APPL_LOGON . . . 33KI2_I1nn_CLASSIC_VTAM_NODE . . . . . . 34KI2_I1nn_CLASSIC_XMIT . . . . . . . . . 35KI2_I1nn_ROW . . . . . . . . . . . . . 36KI2_CLASSIC_ATTCH_CMD_BMP . . . . . . 37KI2_CLASSIC_DED_SESS . . . . . . . . . 38KI2_CLASSIC_SAP_SUPPORT . . . . . . . . 39KI2_CLASSIC_VTAM_CONNECT . . . . . . . 40KI2_CLASSIC_ATFI2 . . . . . . . . . . . 41KI2_CLASSIC_ATF_ATFBUFF . . . . . . . . 42KI2_CLASSIC_ATF_AUTORESTART . . . . . . 43KI2_CLASSIC_ATF_BUFFSIZE . . . . . . . . 44KI2_CLASSIC_ATF_SANDBOX . . . . . . . . 45KI2_CLASSIC_ATF_STOR . . . . . . . . . 46KI2_CLASSIC_ATF_TRACE . . . . . . . . . 47KI2_CLASSIC_DEXAN . . . . . . . . . . 48KI2_CLASSIC_EPILOG . . . . . . . . . . 49KI2_CLASSIC_RTA . . . . . . . . . . . . 50

KI2_CLASSIC_RTA_SLOUGH . . . . . . . . 51KI2_CLASSIC_RTA_XCFGROUP . . . . . . . 52KI2_CLASSIC_TRF . . . . . . . . . . . . 53KI2_CLASSIC_TRF_BMP . . . . . . . . . . 54KI2_CLASSIC_TRF_DBD . . . . . . . . . . 55KI2_CLASSIC_TRF_DB2 . . . . . . . . . . 56KI2_CLASSIC_TRF_DL1 . . . . . . . . . . 57KI2_CLASSIC_TRF_FP . . . . . . . . . . 58KI2_CLASSIC_TRF_LOG . . . . . . . . . . 59KI2_CLASSIC_TRF_LOGREC_ID . . . . . . . 60KI2_CLASSIC_VSAM_MSG_LOG . . . . . . . 61KI2_CLASSIC_RACF_BMP_APPL_GRP . . . . . 62KI2_CLASSIC_RACF_BMP_APPL_GWK. . . . . 63KI2_CUA_OMEGCTR_HILEV . . . . . . . . 64KI2_PSM_ERP_COUNT . . . . . . . . . . 65KI2_MIG_HILEV . . . . . . . . . . . . 66KI2_MIG_OLD_EPILOG_DSTOR . . . . . . . 67KI2_MIG_OLD_EPILOG_OPT . . . . . . . . 68KI2_MIG_OLD_EPILOG_$DEF . . . . . . . . 69KI2_MIG_OLD_EPILOG_@DEF. . . . . . . . 70KI2_MIG_OLD_NAM . . . . . . . . . . . 71KI2_MIG_OLD_PROF . . . . . . . . . . . 72KI2_MIG_OLD_SCRN_SPC . . . . . . . . . 73KI2_MIG_OLD_TDB . . . . . . . . . . . 74KI2_MIG_VER . . . . . . . . . . . . . 75KI2_X_IMS_CONFIRM_SHUTDOWN . . . . . 76KI2_X_IMS_DEBUG_TRACE . . . . . . . . 77KI2_X_IMS_LGSA_VERIFY . . . . . . . . . 78KI2_X_IMS_LOGBLOCK_SIZE . . . . . . . . 79KI2_X_IMS_LSRPOOL_BUFFER_NUM1 . . . . . 80KI2_X_IMS_LSRPOOL_BUFFER_NUM2 . . . . . 81KI2_X_IMS_LSRPOOL_BUFFER_NUM3 . . . . . 82KI2_X_IMS_LSRPOOL_BUFSIZE1 . . . . . . . 83KI2_X_IMS_LSRPOOL_BUFSIZE2 . . . . . . . 84KI2_X_IMS_LSRPOOL_BUFSIZE3 . . . . . . . 85KI2_X_IMS_SDUMP_SVC_SYS1_DUMP . . . . . 86KI2_X_IMS_STORAGE_LIMIT_EXTEND. . . . . 87KI2_X_IMS_STORAGE_LIMIT_PRIMARY . . . . 88KI2_X_IMS_STORAGE_MIN_EXTEND . . . . . 89KI2_X_IMS_STORAGE_MIN_PRIMARY . . . . . 90KI2_X_IMS_STORAGE_RESERVE_EXT . . . . . 91KI2_X_IMS_STORAGE_RESERVE_PRI . . . . . 92KI2_X_IMS_STORAGE_STGDEBUG . . . . . . 93KI2_X_SECURITY_RESOURCE_CLASS . . . . . 94KI2_X_SECURITY_USER_EXIT . . . . . . . . 95KI2_X_STC_INCLUDE_IMSMON_FLAG . . . . 96

Chapter 3. KI5 configurationparameters . . . . . . . . . . . . . 97KI5_II . . . . . . . . . . . . . . . . 99KI5_IInn_ROW . . . . . . . . . . . . . 100KI5_IInn_SSID . . . . . . . . . . . . . 101KI5_IInn_SS_AUTO . . . . . . . . . . . 102KI5_IInn_SS_CONFLICT . . . . . . . . . 103KI5_IInn_SS_COUPFAC . . . . . . . . . . 104

© Copyright IBM Corp. 2012 iii

KI5_IInn_SS_DBCMSK . . . . . . . . . . 105KI5_IInn_SS_DBCTHR . . . . . . . . . . 106KI5_IInn_SS_DEX . . . . . . . . . . . . 107KI5_IInn_SS_DSHR . . . . . . . . . . . 108KI5_IInn_SS_ENV . . . . . . . . . . . . 109KI5_IInn_SS_HADB . . . . . . . . . . . 110KI5_IInn_SS_HLTH . . . . . . . . . . . 111KI5_IInn_SS_LCK . . . . . . . . . . . . 112KI5_IInn_SS_MQSTAT . . . . . . . . . . 113KI5_IInn_SS_MSC . . . . . . . . . . . . 114KI5_IInn_SS_OSAM . . . . . . . . . . . 115KI5_IInn_SS_OTMA . . . . . . . . . . . 116KI5_IInn_SS_PARM . . . . . . . . . . . 117KI5_IInn_SS_POOLS . . . . . . . . . . . 118KI5_IInn_SS_RESOURCE . . . . . . . . . 119KI5_IInn_SS_RGO . . . . . . . . . . . . 120KI5_IInn_SS_RTAETE. . . . . . . . . . . 121KI5_IInn_SS_RTAEXCP . . . . . . . . . . 122KI5_IInn_SS_RTAGRPH . . . . . . . . . . 123KI5_IInn_SS_RTAINTV . . . . . . . . . . 124KI5_IInn_SS_RTARMON . . . . . . . . . 125KI5_IInn_SS_RTASLOT . . . . . . . . . . 126KI5_IInn_SS_SHRQ . . . . . . . . . . . 127KI5_IInn_SS_TYP . . . . . . . . . . . . 128KI5_IInn_SS_WORK . . . . . . . . . . . 129KI5_IInn_SS_ICMD . . . . . . . . . . . 130KI5_COMP . . . . . . . . . . . . . . 131KI5_COMPnn_ICON_NAME . . . . . . . . 132KI5_COMPnn_ROW . . . . . . . . . . . 133KI5_COMPnn_TYPE . . . . . . . . . . . 134KI5_ICT_AUTODISCOVER . . . . . . . . . 135KI5_ICT_BUFFER_SIZE . . . . . . . . . . 136KI5_ICT_BUFFER_THRESH . . . . . . . . 137KI5_ICT_COLLECT_INTERVAL . . . . . . . 138

KI5_ICT_COLLECT_LEVEL . . . . . . . . 139KI5_ICT_MESSAGE_LEVEL . . . . . . . . 140KI5_X_ICT_IMS_CONNECT_FLAG . . . . . . 141KI5_X_AGT_CONFIRM_SHUTDOWN . . . . . 142KI5_X_AGT_DEBUG_TRACE . . . . . . . . 143KI5_X_AGT_KDC_DEBUG . . . . . . . . . 144KI5_X_AGT_LGSA_VERIFY . . . . . . . . 145KI5_X_AGT_LSRPOOL_BUFFER_NUM . . . . 146KI5_X_AGT_LSRPOOL_BUFSIZE. . . . . . . 147KI5_X_AGT_SDUMP_SVC_SYS1_DUMP . . . . 148KI5_X_AGT_STORAGE_LIMIT_EXTEND . . . . 149KI5_X_AGT_STORAGE_LIMIT_PRIMARY. . . . 150KI5_X_AGT_STORAGE_RESERVE_EXT . . . . 151KI5_X_AGT_STORAGE_RESERVE_PRI . . . . . 152KI5_X_AGT_STORAGE_STGDEBUG . . . . . 153KI5_X_AGT_TASKS_ATTACHED_NUM . . . . 154

Appendix A. Documentation library 155OMEGAMON XE for IMS publications . . . . . 155Shared OMEGAMON XE publications . . . . . 156IBM Tivoli Monitoring library . . . . . . . . 156Related publications . . . . . . . . . . . 158

Appendix B. Accessibility . . . . . . 159

Support information . . . . . . . . 161

Notices . . . . . . . . . . . . . . 163Trademarks . . . . . . . . . . . . . . 165

Index . . . . . . . . . . . . . . . 167

iv IBM Tivoli OMEGAMON XE for IMS on z/OS: Parameter Reference

Tables

1. Generating the configuration profile. . . . . 3

© Copyright IBM Corp. 2012 v

vi IBM Tivoli OMEGAMON XE for IMS on z/OS: Parameter Reference

Chapter 1. Overview of configuration parameters

The IBM® Tivoli® OMEGAMON® XE for IMS™ on z/OS® product, the related OMEGAMON II for IMSproduct, and the OMEGAMON Enhanced 3270 User Interface components use parameters to set andstore configuration values.

While the interactive or batch mode in the Configuration Tool (ICAT) is a valid configuration method, thePARMGEN configuration method is the preferred method of product configuration. With the PARMGENmethod, you edit a comprehensive list of parameters for configuring all installed products andcomponents. You then submit a series of jobs to create a complete runtime environment with theparameter values that you specified. If you have runtime environments that are already configured by theConfiguration Tool (ICAT) method, you can use a conversion tool to convert existing parameter values inthose runtime environments to set up initial values for new runtime environments to be configured bythe PARMGEN method.

Information is available about each parameter for the OMEGAMON XE for IMS on z/OS product, theOMEGAMON II for IMS product, and the OMEGAMON enhanced 3270 user interface component. Youare provided with a description of the parameter, its name in both BATCH and PARMGEN configurationmethods, and how you can locate the parameter in the Configuration Tool by name, panel, panel ID, andfield.

Attention: Do not attempt to configure this product using only this guide. This reference guidesupplements the information in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:Common Planning and Configuration Guide. You must perform many of the pre- and post-configurationtasks described in the common configuration guide and in the IBM Tivoli OMEGAMON XE for IMS onz/OS: Planning and Configuration Guide regardless of whether you use the PARMGEN or the ConfigurationTool configuration method.

For more information about using the PARMGEN configuration method, see the following resources:v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration

Guide

v Definitions of common parameters, such as those used by runtime environments (RTE parameters)and Tivoli Enterprise Monitoring Server, are available in the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Parameter Reference

v For a technical overview of the PARMGEN configuration method, see IBM Tivoli OMEGAMON XE andTivoli Management Services on z/OS: Parameter Reference and the PARMGEN Technoteathttp://www.ibm.com/support/docview.wss?uid=swg21417935

Location of stored configuration parametersMost OMEGAMON XE for IMS on z/OS configuration parameters and their configured values are storedin the KI5ENV, KI2SYSIN, or KI5SYSIN members of the &rhilev.&midlev.&rtename.RKANPARU data setsfor each runtime environment, where &rhilev is the runtime high-level qualifier, &midlev is the mid-levelqualifier, and &rtename is the name of the runtime environment. The members are prefixed with theproduct component prefix, where KI5 is OMEGAMON XE for IMS on z/OS and KI2 is OMEGAMON IIfor IMS (CUA).

The parameters that are stored in the KI5ENV member are environment variables that determine theoperating characteristics of the runtime environment in which products and components are configured.The parameters stored in the KI2SYSIN and KI5SYSIN members are startup parameters that determinethe default startup values for each product or component.

© Copyright IBM Corp. 2012 1

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

Some environment variables and startup parameters are stored in members other than KI5ENV andKI2SYSIN or KI5SYSIN, or in data sets other than RKANPARU. Some data set members are RKANSAMUdata set members, for example, KI2_CUA_STC, and some additional parameters are neither environmentvariables nor startup parameters, but must be included in the runtime libraries for the products andcomponents to operate correctly.

Parameter namesParameters can have different names, such as the Configuration Tool name or BATCH parameter name.

Most parameters have several different names:

Stored Parameter nameName of the parameter as stored in a runtime library. Example: *EXEC KI2ATFmp

Configuration Tool field nameName of the field that identifies the parameter on an interactive panel. Example: ApplicationTrace Facility

Batch parameter nameName of the parameter in the batch parameter member. Example: KI2_CLA_ATFI2

PARMGEN nameName of the parameter in the PARMGEN parameter list. Example: KI2_CLASSIC_ATFI2

Note: Batch parameter names and PARMGEN names are usually different. In this instance, theyare similar.

This reference guide describes the parameter names for this monitoring agent. To investigate the completelist of names for the runtime environment and Tivoli Enterprise Monitoring Server parameters, see IBMTivoli OMEGAMON XE and Tivoli Management Services on z/OS: Parameter Reference.

Parameters containing n or nn

The names of some parameters include n or nn. Note that these are not the actual names of thesecommands that you see in the configuration profile (your given rte_name). The n or nn means that youcan have multiple instances of this parameter in your configuration profile. For example, you might havemultiple instances of KI5_IInn values if multiple IMS subsystems are defined. If you cannot find aparameter by searching on its full name, omit the numbers that define its instance and try searching on apart of the parameter.

Parameters used by the PARMGEN configuration methodThe comprehensive list of parameters for this monitoring agent are grouped logically in the PARMGENconfiguration profile.

The PARMGEN configuration method is the preferred, primary way to configure the Tivoli ManagementServices on z/OS components and the OMEGAMON XE products. It is particularly suitable for newOMEGAMON XE customers who are already accustomed to supplying parameter values directly in theSYS1.PARMLIB data set, or for existing OMEGAMON XE customers in environments in which oneperson is responsible for configuring all OMEGAMON XE products and components.

If you have runtime environments that are already configured by the Configuration Tool, run theconversion utility (the KCIJPCNV job) on the existing parameter values in your runtime environment andset up initial values for a new runtime environment to be configured by the PARMGEN method. Theseparameters are found in the configuration profile, which can be generated from an existing RTE. If this isa new installation or if you do not want to base the configuration profile on an existing RTE, you can edita default configuration profile.

2 IBM Tivoli OMEGAMON XE for IMS on z/OS: Parameter Reference

After you use the PARMGEN method to configure new runtime environments, you cannot use theConfiguration Tool to edit or maintain the parameter values. See the IBM Tivoli OMEGAMON XE andTivoli Management Services on z/OS: Common Planning and Configuration Guide for information about usingthis utility.

Generating and editing the configuration profileA PARMGEN configuration profile, which is given the runtime environment name, contains parametervalues for all the parameters in a runtime environment.

You can set up a configuration profile from any of the following inputs:v You can use the initial values provided by IBM in the configuration profile member of the WCONFIG

work control library as input. This method is most suitable for new customers who do not alreadyhave a configured runtime environment.

v If you have a runtime environment that is already configured by the Configuration Tool (ICAT)method and you want to use the batch parameter values of that runtime environment, you can run aconversion tool and use the existing parameter values as initial PARMGEN parameter values.Attention: After you convert the batch parameter member and then use the PARMGEN method toconfigure a new runtime environment, you cannot use the Configuration Tool to edit or maintain theconfiguration.

v You can create a new runtime environment batch parameter member in the WCONFIG library, and usethe values in the batch parameter member as initial PARMGEN parameter values.

Complete the steps that are appropriate to your environment, as shown in the following table.

Table 1. Generating the configuration profile

User type Steps

If you are a user migrating from the Configuration Toolmethod to the PARMGEN method

1. Run the conversion tool to create an initialconfiguration profile file that contains your previousconfiguration. The resulting configuration profile file,stored in the WCONFIG library, is the z/OS text filethat contains all the parameters for all theOMEGAMON monitoring agents on z/OS that youhave installed in your environment.

2. Edit the configuration profile file to introduce anychanges you want to make to your global orstack-specific values, using this reference guide tohelp you understand the agent-specific parameters.

3. To configure your instances of this monitoring agentusing the PARMGEN configuration method, followthe process that describes how to use the PARMGENmethod to set parameter values in the IBM TivoliOMEGAMON XE and Tivoli Management Services onz/OS: Common Planning and Configuration Guide.

If you are a new user of OMEGAMON monitoringagents

1. Edit the sample configuration profile in theWCONFIG library to contain only those agentsinstalled in this runtime environment.

2. Follow the process described in the IBM TivoliOMEGAMON XE and Tivoli Management Services onz/OS: Common Planning and Configuration Guide.

Chapter 1. Overview of configuration parameters 3

Parameters in the Configuration ToolThe interactive Configuration Tool was the original method used to define the configuration parametersfor OMEGAMON XE for IMS on z/OS. Although it is still in use today as a valid configuration method,the PARMGEN method is the preferred configuration method.

If you use the Configuration Tool in interactive mode, you configure the runtime environments,monitoring agents, and infrastructure components by accepting defaults or supplying values in fields onConfiguration Tool panels.v To set up the Configuration Tool and use it to configure Tivoli Enterprise Monitoring Server on z/OS,

see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning andConfiguration Guide.

v To use the Configuration Tool to configure OMEGAMON XE for IMS on z/OS, or OMEGAMON II forIMS, see the IBM Tivoli OMEGAMON XE for IMS on z/OS: Planning and Configuration Guide.

Parameters in batch mode processingValues that you define with the Configuration Tool can be replicated to other z/OS images using batchmode processing.

After you have used the Configuration Tool in interactive mode to configure a runtime environment, youcan use the tool in batch mode processing (CICATB) to replicate that environment to other z/OS images.Using batch mode processing, you can install a complete runtime environment by submitting a singlebatch job, rather than configuring it panel by panel.

The principal components of batch mode processing are the batch mode job and the batch parametermember. The batch mode job validates the input configuration parameters and generates the jobsrequired to build, configure, and load a runtime environment. The job uses a single parameter membercontaining all the configuration parameters as input for the jobs it generates. The parameter member isderived from an existing runtime environment using a Configuration Tool utility. You can adjust theparameters before using the parameter member to create a new runtime environment or to configureagain or restore an existing one.

You can use the parameters described in this reference guide to propagate your configuration throughoutyour enterprise via batch mode processing.

For information about running batch mode processing, see the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Common Planning and Configuration Guide. For reference information aboutthe parameters used in configuring OMEGAMON XE for IMS on z/OS, see this guide and theConfiguration Tool help panels and parameter maps. See the section that describes how to obtainparameter reports in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide.

Default valuesThe monitoring agent and all components default to pre-defined values.

Some parameters have only one default value, and some have more than one. For example, TMS:Engine(Tivoli Monitoring Services:Engine) sets this global default value for the KIS_TEMS_STORAGE_LIMIT_EXTENDparameter:LIMIT(16,X)

However, the Configuration Tool panels and PARMGEN files override the TMS:Engine default and showa 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 valueoverrides the Configuration Tool or PARMGEN default value, which has already overridden theTMS:Engine default value if a TMS:Engine default value exists. So if you configured your environmentusing PARMGEN, the value for the KIS_TEMS_STORAGE_LIMIT_EXTEND parameter is 23.

The OMEGAMON XE for IMS on z/OS monitoring agent KI5_X_AGT_STORAGE_LIMIT_EXTEND parameterhas this default value.LIMIT(23,X)

If the monitoring agent is configured in the Tivoli Enterprise Monitoring Server address space, the TivoliEnterprise Monitoring Server value applies to both the Tivoli Enterprise Monitoring Server and themonitoring agent, and the monitoring agent does not have its own value. If the monitoring agent isconfigured stand-alone, then the monitoring agent value for each parameter overrides the TMS:Enginevalue, and the Tivoli Enterprise Monitoring Server value has no effect on the monitoring agent.

Default values for runtime environment and Tivoli Enterprise Monitoring Server parameters aredocumented in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: ParameterReference. Default values for this monitoring agent are documented in this guide and are shown in theConfiguration Tool panels, batch mode data dictionaries, and parameter maps. See the section thatdescribes how to obtain parameter reports in the IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide.

Chapter 1. Overview of configuration parameters 5


Chapter 2. KI2 configuration parameters

The configuration parameters for the OMEGAMON II for IMS (3270) and OMEGAMON II for IMS (CUA)interface are grouped logically in the configuration file.

An overview of the parameters found in the OMEGAMON II for IMS section of the PARMGENconfiguration profile follows. The prefix associated with OMEGAMON XE for IMS is KI2.

The KI2_* parameters control both the OMEGAMON II for IMS (CUA) and OMEGAMON II for IMS(3270) component configuration, and generate KI2 and KIP prefixed members where applicable.

The following parameters are classified in the order in which the parameters exist in PARMGEN:v OMEGAMON II (CUA) and OMEGAMON for IMS (3270) options

– “KI2_CLASSIC_STC_PREFIX” on page 10– “KI2_CLASSIC_UMAX” on page 11– “KI2_CLASSIC_VTAM_APPL_PREFIX” on page 12– “KI2_CLASSIC_VTAM_NODE_PREFIX” on page 13– “KI2_CUA_STC” on page 14– “KI2_CUA_VTAM_APPL_CMD” on page 15– “KI2_CUA_VTAM_APPL_I/CF” on page 16– “KI2_CUA_VTAM_APPL_LOGON” on page 17– “KI2_CUA_VTAM_APPL_OPERATOR” on page 18– “KI2_CUA_VTAM_APPL_PREFIX” on page 19– “KI2_CUA_VTAM_NODE” on page 20– “KI2_CUA_VTAM_VTPOOL_NUM” on page 21– “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22– “KI2_CUA_WTO_MSG” on page 23

v The number of OMEGAMON II (CUA) and OMEGAMON for IMS (3270) pairs to monitor– “KI2_CLASSIC_STC_NUM” on page 24

v The OMEGAMON II (CUA) and OMEGAMON for IMS (3270) pairs to monitor table entries– “KI2_I1” on page 25– “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26– “KI2_I1nn_CLASSIC_IMSID” on page 27– “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28– “KI2_I1nn_CLASSIC_LROWS” on page 29– “KI2_I1nn_CLASSIC_MPREFIX” on page 30– “KI2_I1nn_CLASSIC_STC” on page 31– “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32– “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33– “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34– “KI2_I1nn_CLASSIC_XMIT” on page 35– “KI2_I1nn_ROW” on page 36

v OMEGAMON for IMS 3270 connection options– “KI2_CLASSIC_ATTCH_CMD_BMP” on page 37– “KI2_CLASSIC_DED_SESS” on page 38– “KI2_CLASSIC_SAP_SUPPORT” on page 39– “KI2_CLASSIC_VTAM_CONNECT” on page 40

v OMEGAMON for IMS 3270 data collection options– “KI2_CLASSIC_ATFI2” on page 41– “KI2_CLASSIC_ATF_ATFBUFF” on page 42– “KI2_CLASSIC_ATF_AUTORESTART” on page 43– “KI2_CLASSIC_ATF_BUFFSIZE” on page 44


– “KI2_CLASSIC_ATF_SANDBOX” on page 45– “KI2_CLASSIC_ATF_STOR” on page 46– “KI2_CLASSIC_ATF_TRACE” on page 47– “KI2_CLASSIC_DEXAN” on page 48– “KI2_CLASSIC_EPILOG” on page 49– “KI2_CLASSIC_RTA” on page 50– “KI2_CLASSIC_RTA_SLOUGH” on page 51– “KI2_CLASSIC_RTA_XCFGROUP” on page 52– “KI2_CLASSIC_TRF” on page 53– “KI2_CLASSIC_TRF_BMP” on page 54– “KI2_CLASSIC_TRF_DBD” on page 55– “KI2_CLASSIC_TRF_DB2” on page 56– “KI2_CLASSIC_TRF_DL1” on page 57– “KI2_CLASSIC_TRF_FP” on page 58– “KI2_CLASSIC_TRF_LOG” on page 59– “KI2_CLASSIC_TRF_LOGREC_ID” on page 60– “KI2_CLASSIC_VSAM_MSG_LOG” on page 61

v BMP application group information– “KI2_CLASSIC_RACF_BMP_APPL_GRP” on page 62– “KI2_CLASSIC_RACF_BMP_APPL_GWK” on page 63

v High-level qualifier used in z/OS automation interface exit– “KI2_CUA_OMEGCTR_HILEV” on page 64

v Error recovery information– “KI2_PSM_ERP_COUNT” on page 65

v Migration options– “KI2_MIG_HILEV” on page 66– “KI2_MIG_OLD_EPILOG_DSTOR” on page 67– “KI2_MIG_OLD_EPILOG_OPT” on page 68– “KI2_MIG_OLD_EPILOG_$DEF” on page 69– “KI2_MIG_OLD_EPILOG_@DEF” on page 70– “KI2_MIG_OLD_NAM” on page 71– “KI2_MIG_OLD_PROF” on page 72– “KI2_MIG_OLD_SCRN_SPC” on page 73– “KI2_MIG_OLD_TDB” on page 74– “KI2_MIG_VER” on page 75

v Additional OMEGAMON II for IMS settings– “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76– “KI2_X_IMS_DEBUG_TRACE” on page 77– “KI2_X_IMS_LGSA_VERIFY” on page 78– “KI2_X_IMS_LOGBLOCK_SIZE” on page 79– “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80– “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81– “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82– “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83– “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84– “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85– “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86– “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87– “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88– “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89– “KI2_X_IMS_STORAGE_MIN_PRIMARY” on page 90– “KI2_X_IMS_STORAGE_RESERVE_EXT” on page 91– “KI2_X_IMS_STORAGE_RESERVE_PRI” on page 92– “KI2_X_IMS_STORAGE_STGDEBUG” on page 93– “KI2_X_SECURITY_RESOURCE_CLASS” on page 94


– “KI2_X_SECURITY_USER_EXIT” on page 95– “KI2_X_STC_INCLUDE_IMSMON_FLAG” on page 96

Chapter 2. KI2 configuration parameters 9

KI2_CLASSIC_STC_PREFIXUse the KI2_CLASSIC_STC_PREFIX parameter to specify the started task prefix that generates the startedtask procedure names for each of the Realtime Monitor (RTM) tasks.

Required or optionalRequired

Location where the parameter value is storedThe parameter value is not stored, but it is used to generate started task procedure names.

Parameter nameI2RTPRDF

Default valueCANSOI

Permissible valuesA character string no longer than six characters in length

In the Configuration Tool (ICAT)

Panel nameSPECIFY RTM CONFIGURATION VALUES / RTE: rtename

Panel IDKI256PN

Field Started task prefix

Default valueCANSOI

Permissible valuesA character string no longer than sixcharacters in length

Batch parameter nameKI2_CLA_STC_PREF


KI2_CLASSIC_UMAXUse the KI2_CLASSIC_UMAX parameter to specify the maximum number of concurrent sessions that thecollector can support. Make sure that you have enough sessions to support all of the menu,OMEGAMON II (CUA) interface, and OMEGAVIEW sessions for multiple IMS regions.


Location where the parameter value is storedThe KOIVTMmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameUMAX=&I2UMAX

Default value99

Permissible values1 - 99



Panel IDKI256PN

Field Maximum number of RTM users (UMAX)

Default value99


Batch parameter nameKI2_CLA_UMAX


KI2_CLASSIC_VTAM_APPL_PREFIXUse the KI2_CLASSIC_VTAM_APPL_PREFIX parameter to generate VTAM® APPLIDs for theOMEGAMON for IMS (3270) virtual terminal, also known as the collector. The engine operator facilityuses the virtual terminals to connect the OMEGAMON II (CUA) interface with the collectors.


Location where the parameter value is storedThe parameter value is not stored, but it is used to generate VTAM APPLIDs for OMEGAMONfor IMS (3270) virtual terminals.

Parameter name&X2RTAPDF

Default valueCTDOIn

Permissible values



Panel IDKI256PN

Field Classic logon prefix

Default valueCTDOIn

Batch parameter nameKI2_CLA_VTM_APPL_PREF

Related parametersv “KI2_CLASSIC_VTAM_NODE_PREFIX” on page 13


KI2_CLASSIC_VTAM_NODE_PREFIXUse the KI2_CLASSIC_VTAM_NODE_PREFIX parameter to specify the VTAM major node used in theRTM PROC member to generate the VTAM node definition member.


Location where the parameter value is storedThe parameter value is not stored, but it is used to generate the VTAM node definition member.

Parameter name&X2RTMJDF

Default valueCTDOInN

Permissible values



Panel IDKI256PN

Field Major node prefix

Default valueCTDOInN

Batch parameter nameKI2_CLA_VTM_NODE_PREF

Related parametersv “KI2_CLASSIC_VTAM_APPL_PREFIX” on page 12


KI2_CUA_STCUse the KI2_CUA_STC parameter to specify the name of the OMEGAMON II for IMS (CUA) started taskon the monitored system. You must copy this started task to your system procedure library.

Required or optionalOptional

Location where the parameter value is storedThe &I2CUAPRC member of the rhilev.midlev.rtename.xKANSAMU library where x is R, W or I.

Parameter name&I2CUAPRC PROC

Default valueCANSI2

Permissible valuesSee the IBM JCL Reference Guide for a list of STC naming conventions.


Panel nameSPECIFY CUA CONFIGURATION VALUES / RTE: rtename

Panel IDKI256PP

Field Started task

Default valueCANSI2

Permissible valuesSee the IBM JCL Reference Guide for a list of STC naming conventions.

Batch parameter nameKI2_CUA_STC


KI2_CUA_VTAM_APPL_CMDUse the KI2_CUA_VTAM_APPL_CMD parameter to specify the APPLID required to issue VTAMcommands through the engine operator facility.


Location where the parameter value is storedThe CTDI2N member of the rhilev.midlev.rtename.xKANSAMU library and the KI2INVPO memberof the rhilev.midlev.rtename.xKANSAMU library, where x is R, W or I.

Parameter nameKI2INVPO: &X2CUCAPP SHARE(16)

CTDI2N: &X2CUCAPP APPL

Default valueCTDI2VP

Permissible values


Panel nameSPECIFY VTAM APPLID VALUES / RTE: rtename

Panel IDKI256PQ

Field TMS:Engine VTAM program operator

Default valueCTDI2VP

Permissible values

Batch parameter nameKI2_CUA_VTM_APPL_CMD

Related parametersv “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_APPL_I/CFUse the KI2_CUA_VTAM_APPL_I/CF parameter to specify the VTAM APPLID required to directly logon to the OMEGAMON II for IMS I/CF master console. This APPLID is used for I/CF Console and I/CFTrap commands.


Location where the parameter value is storedThe CTDI2N member of the rhilev.midlev.rtename.xKANSAMU library and the KI2START memberof the rhilev.midlev.rtename.xKANCMDU library, where x is R, W or I.

Parameter nameKI2START: DIALOG &X2ICFAPP KI2PICF

CTDI2N: &X2ICFAPP APPL

Default valueCTDI2IC

Permissible values



Panel IDKI256PQ

Field I/CF master console

Default valueCTDI2IC

Batch parameter nameKI2_CUA_VTM_APPL_I/CF

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_APPL_LOGONUse the KI2_CUA_VTAM_APPL_LOGON parameter to specify the VTAM APPLID for the OMEGAMONII (CUA) interface, to log on to the OMEGAMON II for IMS(3270) interface, and to connect toOMEGAVIEW with the OMEGAMON II for IMS interface.



Parameter nameKI2START: DIALOG &X2CUAPPL KI2PLOG

CTDI2N: &X2CUAPPL APPL

Default valueCTDI2AP

Permissible values



Panel IDKI256PQ

Field CUA logon

Default valueCTDI2AP

Batch parameter nameKI2_CUA_VTM_APPL_LOGON

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_APPL_OPERATORUse the KI2_CUA_VTAM_APPL_OPERATOR parameter to specify the VTAM APPLID for the engineoperator facility. You can use the VTAM APPLID to log on to the user interface under the guidance ofIBM Software Support.



Parameter nameKI2START: DIALOG &X2OPRAPP KLVLOGON

CTDI2N: &X2OPRAPP APPL

Default valueCTDI2OP

Permissible values



Panel IDKI256PQ

Field TMS:Engine operator logon

Default valueCTDI2OP

Batch parameter nameKI2_CUA_VTM_APPL_OPR

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_APPL_PREFIXUse the KI2_CUA_VTAM_APPL_PREFIX parameter to specify the APPLID prefix required to constructthe VTAM node and APPLIDs for the OMEGAMON II (CUA) interface.


Location where the parameter value is storedThe parameter value is not stored, but it is used to generate VTAM nodes and APPLIDs for theOMEGAMON II (CUA) interface.

Parameter name&X2APLPFX

Default valueCTDI2

Permissible values



Panel IDKI256PP

Field Applid prefix

Default valueCTDI2

Batch parameter nameKI2_CUA_VTM_APPL_PREF

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_NODEUse the KI2_CUA_VTAM_NODE parameter to specify the VTAM major node required in the CUA PROCmember to generate the VTAM node definition member.


Location where the parameter value is storedThe &X2CUMJND member of the rhilev.midlev.rtename.xKANSAMU library where x is R, W or I.

Parameter name&X2CUMJND VBUILD TYPE=APPL

Default valueCTDI2N

Permissible values



Panel IDKI256PQ

Field Major node

Default valueCTDI2

Permissible values

Batch parameter nameKI2_CUA_VTM_NODE

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_VTPOOL_NUMUse the KI2_CUA_VTAM_VTPOOL_NUM parameter to specify the maximum number of APPLIDs in thevirtual terminal pool that the OMEGAMON II for IMS (CUA) requires to connect to the classic RealtimeMonitor (RTM) address spaces. Each RTM task connection requires four virtual terminal APPLIDs.Therefore, you must specify enough definitions in the pool to accommodate each RTM task.



Parameter nameKI2START: TH(&I2CUACNT)

CTDI2N: CTDI201 APPL through CTDI2nn APPL where nn is the value for &I2CUACNTspecified in KI2START

Default value99




Panel IDKI256PP

Field Maximum number of CUA users

Default value99


Batch parameter nameKI2_CUA_VTM_VTRM_NUM

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_PREFIX” on page 22


KI2_CUA_VTAM_VTPOOL_PREFIXUse the KI2_CUA_VTAM_VTPOOL_PREFIX parameter to specify the virtual terminal prefix required togenerate the OMEGAMON II (CUA) virtual terminal APPLIDs, which connect with the classic RealtimeMonitor (RTM) address spaces.


Location where the parameter value is storedThe parameter value is not stored, but it is used to generate OMEGAMON II (CUA) virtualterminal APPLIDs.

Parameter name&X2CUAPFX

Default valueCTDI2

Permissible values



Panel IDKI256PP

Field Virtual terminal prefix

Default valueCTDI2

Batch parameter nameKI2_CUA_VTM_VTRM_PREF

Related parametersv “KI2_CUA_VTAM_APPL_CMD” on page 15v “KI2_CUA_VTAM_APPL_I/CF” on page 16v “KI2_CUA_VTAM_APPL_LOGON” on page 17v “KI2_CUA_VTAM_APPL_PREFIX” on page 19v “KI2_CUA_VTAM_APPL_OPERATOR” on page 18v “KI2_CUA_VTAM_NODE” on page 20v “KI2_CUA_VTAM_VTPOOL_NUM” on page 21


KI2_CUA_WTO_MSGUse the KI2_CUA_WTO_MSG parameter to issue Write To Operator (WTO) messages from the CUAaddress space. WTO messages write information and exception condition messages to the operatorconsoles for you to view. Alert messages are always written to the consoles.


Location where the parameter value is storedThe KI2SYSIN member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameWTO(&I2WTO)

Default valueN

Permissible valuesY or N



Panel IDKI256PP

Field Enable WTO messages

Default valueN


Batch parameter nameKI2_CUA_WTO_MSG


KI2_CLASSIC_STC_NUMUse the KI2_CLASSIC_STC_NUM parameter to specify the number of Realtime Monitor (RTM) tasks.OMEGAMON II consists of one address space and a RTM address space for each IMS region. Each RTMtask monitors a single IMS region. The field value should be the number of IMS regions that you plan tomonitor.


Location where the parameter value is stored

Parameter name&I2RTTCNT

Default value1



Panel nameSPECIFY RTM CONFIGURATION VALUES/ RTE: rtename

Panel IDKI256PN

Field Number of tasks

Default value1


Batch parameter nameKI2_CLA_STC_NUM


KI2_I1Use the KI2_I1 parameter to specify the beginning or end of the Realtime Monitor (RTM) task groupinformation. If the variable value is BEGIN, the variables that follow are used to construct rows in a tablecontaining information for an RTM Task. If the variable value is END, it indicates the end of the RTMgroup information.



Parameter nameN/A

Default valueBEGIN

Permissible valuesBEGIN or END


Default valueBEGIN


Batch parameter nameKI2_I1

Related parametersv “KI2_I1nn_ROW” on page 36v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_XMIT” on page 35


KI2_I1nn_CLASSIC_CTRL_UNIT_ADDRUse the KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR parameter to specify the control unit address to be usedin KOIDEDmp.


Location where the parameter value is storedThe KOIDEDmp member of the rhilev.midlev.rtename.xKANPARU library where x is R, W or I.

Parameter nameSTART SESSION UNIT=&I2RTCUAA

Default valueXXXX

Permissible valuesCharacter string no longer than eight characters in length


Panel nameREALTIME MONITOR PARAMETERS/ RTE: rtename

Panel IDKI256PB / KI256PBV

Field CU-Addr

Default valueXXXX


Batch parameter nameKI2_I1_CLA_CU_ADDR

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_IMSIDUse the KI2_I1nn_CLASSIC_IMSID parameter to specify the IMSID in the Realtime Monitor (RTM)procedure, which identifies the associated IMS. This field is also used to qualify the names of those datasets that must be unique to each RTM.


Location where the parameter value is storedThe KI2START member of the rhilev.midlev.rtename.xKANCMDU library where x is R, W or I.

Parameter nameIMSID(&I2RTIMSA)

Default valueIMnn where nn is constructed as follows:

Number of RTM tasks <= 16: nn = SA...SP

Number of RTM tasks > 16: nn = N0...N9 - V0...V2

Permissible valuesCharacter string no longer than four characters in length




Field IMSID

Default valueIMnn where nn is constructed as follows:

Number of RTM tasks <= 16: nn = SA...SP

Number of RTM tasks > 16: nn = N0...N9 - V0...V2


Batch parameter nameKI2_I1_CLA_IMSID

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_IMS_RESLIBUse the KI2_I1nn_CLASSIC_IMS_RESLIB parameter to specify the IMS RESLIB data set required for theBMP interface.


Location where the parameter value is storedThe &I2OIPROC member of the rhilev.midlev.rtename.xKANSAMU library where x is R, W or I.

Parameter nameDSN=&I2RTIMSR

Default valueIMS.RESLIB

Permissible valuesCharacter string no longer than 44 characters in length




Field RESLIB-DSN

Default valueIMS.RESLIB


Batch parameter nameKI2_I1_CLA_IMS_RESLIB

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_LROWSUse the KI2_I1nn_CLASSIC_LROWS parameter to specify the default number of LROWS for anOMEGAMON II for IMS (3270) session.


Location where the parameter value is storedThe KOIDEDmp member of the rhilev.midlev.rtename.xKANPARU library and the KOIVTMmpmember of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameLROWS=&I2LROWS

Default value255

Permissible valuesNumeric string, no longer than four digits



Panel IDKI256PB

Field LROWS

Default value255

Permissible valuesNumeric string, no longer than four digits

Batch parameter nameKI2_I1_CLA_LROWS

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_MPREFIXUse the KI2_I1nn_CLASSIC_MPREFIX parameter to specify the MPREFIX value required as the suffix forall unique members that each Realtime Monitor (RTM) task needs, including the GLOBAL member. TheMPREFIX value is used in the JCL member for the MPREFIX parameter value and in the RKANPARU,RKANSAMU and RKANCMDU members. It is also used for the GLOBAL value in KOIDEDmp, and inKOIGBLmp, where mp is the unique MPREFIX value for each RTM task.


Location where the parameter value is storedThe KI2START member of the rhilev.midlev.rtename.xKANCMDU library where x is R, W or I.

Parameter nameSESSIONNAME(IMS SYSTEM &I2RTSUFF - &I2RTIMSA)

Default valuexn where xn is generated as follows:

Number of RTM tasks <= 16: xn = M0...MF

Number of RTM tasks > 16: xn = N0...N9 – V0...V2

Permissible values16 to 25




Field MPREFIX

Default valuexn where xn is generated as follows:

Number of RTM tasks <= 16: xn = M0...MF

Number of RTM tasks > 16: xn = N0...N9 – V0...V2


Batch parameter nameKI2_I1_CLA_MPREF

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_STCUse the KI2_I1nn_CLASSIC_STC parameter to specify the started task procedure name for a RealtimeMonitor (RTM).


Location where the parameter value is storedThe &I2OIPROC member of the rhilev.midlev.rtename.xKANSAMU library where x is R, W or I.

Parameter name//&I2OIPROC PROC

Default valueCANSOIx where x is constructed as follows:

Number of RTM tasks <= 16: x = 0...F

Number of RTM tasks > 16: x = N0...N9 – V0...V2





Field RTM-PROC

Default valueCANSOIx where x is constructed as follows:

Number of RTM tasks <= 16: x = 0...F



Batch parameter nameKI2_I1_CLA_STC

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_USER_PROFILEUse the KI2_I1nn_CLASSIC_USER_PROFILE parameter to specify the default user profile for aOMEGAMON II for IMS (3270) session.


Location where the parameter value is storedThe KOIDEDmp member of the rhilev.midlev.rtename.xKANPARU library and the KOIVTMmpmember of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameUSER=&I2USER

Default value/C

Permissible valuesCharacter string no longer than two characters in length



Panel IDKI256PB

Field User

Default value/C

Permissible valuesCharacter string no longer than two characters in length

Batch parameter nameKI2_I1_CLA_USER_PROF

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_VTAM_APPL_LOGONUse the KI2_I1nn_CLASSIC_VTAM_APPL_LOGON parameter to specify the VTAM APPLID required inthe VTAM mode definition member.


Location where the parameter value is storedThe KI2START member of the rhilev.midlev.rtename.xKANCMDU library and the KOIVTMmpmember of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameKI2START: APPLID(&X2RTAPPL)

KOIVTMmp: APPL=(&X2RTAPPL)

Default valueCTDOIx where x is constructed as follows:

Number of RTM tasks <= 16: x = 0...F.

Number of RTM tasks > 16: x = N0..,N9 – V0.,.V2




Panel IDKI256PB

Field VTAM Logon applid

Default valueCTDOIx where x is constructed as follows:


Number of RTM tasks > 16: x = N0..,N9 – V0.,.V2


Batch parameter nameKI2_I1_CLA_VTM_APPL_LOGON

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_VTAM_NODEUse the KI2_I1nn_CLASSIC_VTAM_NODE parameter to specify the VTAM major node required in theRTM PROC member and to name the VTAM node definition member.


Location where the parameter value is storedThe &X2RTMJND member of the rhilev.midlev.rtename.xKANSAMU library and the &I2OIPROCmember of the rhilev.midlev.rtename.xKANSAMU library, where x is R, W or I.

Parameter name&X2RTMJND: &X2RTMJND VBUILD TYPE=APPL

&I2OIPROC: VARY NET,ACT,ID=&X2RTMJND

Default valueCTDOIxN where x is constructed as follows:






Panel IDKI256PB

Field VTAM Major node

Default valueCTDOIxN where x is constructed as follows:




Batch parameter nameKI2_I1_CLA_VTM_NODE

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_XMIT” on page 35v “KI2_I1nn_ROW” on page 36


KI2_I1nn_CLASSIC_XMITUse the KI2_I1nn_ROW parameter to specify a unique numeric identifier for this entry in the table.



Parameter name&I2T1OCID

Default value00





Field ID

Default value00


Batch parameter nameKI2_I1_CLA_XMIT

Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_ROW” on page 36


KI2_I1nn_ROWUse the KI2_I1nn_ROW parameter to specify the beginning or end of a single Realtime Monitor (RTM)task entry. If the variable value is BEGIN, the variables up to the next BEGIN or to the next END containall the information necessary to construct a single RTM task entry.



Parameter nameN/A

Default valueBEGIN



Default valueBEGIN


Related parametersv “KI2_I1” on page 25v “KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR” on page 26v “KI2_I1nn_CLASSIC_IMSID” on page 27v “KI2_I1nn_CLASSIC_IMS_RESLIB” on page 28v “KI2_I1nn_CLASSIC_LROWS” on page 29v “KI2_I1nn_CLASSIC_MPREFIX” on page 30v “KI2_I1nn_CLASSIC_STC” on page 31v “KI2_I1nn_CLASSIC_USER_PROFILE” on page 32v “KI2_I1nn_CLASSIC_VTAM_APPL_LOGON” on page 33v “KI2_I1nn_CLASSIC_VTAM_NODE” on page 34v “KI2_I1nn_CLASSIC_XMIT” on page 35


KI2_CLASSIC_ATTCH_CMD_BMPUse the KI2_CLASSIC_ATTCH_CMD_BMP parameter to automatically attach the command BMP. A valueof 'N' adds the asterisk before the EXEC statement, which prevents attaching the command BMPautomatically. Note that this does not apply to DBCTL users.


Location where the parameter value is storedThe KOImpP00 member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter name*EXEC KI2BMPmp

Default valueY




Panel IDKI256PN

Field Attach command BMP

Default valueY


Batch parameter nameKI2_CLA_ATTCH_CMD_BMP


KI2_CLASSIC_DED_SESSUse the KI2_CLASSIC_DED_SESS parameter to automatically start the Realtime Monitor (RTM) dedicatedsession. A value of 'Y' removes the asterisk before the EXEC statement, which enables the session to startautomatically.



Parameter name*EXEC KOIDEDmp

Default valueN




Panel IDKI256PN

Field Dedicated session

Default valueN


Batch parameter nameKI2_CLA_DED_SESS


KI2_CLASSIC_SAP_SUPPORTUse the KI2_CLASSIC_SAP_SUPPORT parameter to automatically start SAP support. A value of 'Y'removes the asterisk before the EXEC statement, which enables SAP support to start automatically. Notethat this does not apply to DBCTL users.



Parameter name*EXEC KOISAPmp

Default valueN




Panel IDKI256PN

Field SAP support

Default valueN


Batch parameter nameKI2_CLA_SAP_SUPPORT


KI2_CLASSIC_VTAM_CONNECTUse the KI2_CLASSIC_VTAM_CONNECT parameter to automatically start the Realtime Monitor (RTM)VTAM to IMS region connection. A value of 'N' adds an asterisk before the EXEC statement, whichprevents the connection from starting automatically.



Parameter name*EXEC KOIVTMmp

Default valueY




Panel IDKI256PN

Field VTAM connection

Default valueY


Batch parameter nameKI2_CLA_VTM_CONNECT


KI2_CLASSIC_ATFI2Use the KI2_CLASSIC_ATFI2 parameter to automatically start the Application Trace Facility (ATF). Avalue of 'Y' removes the asterisk before the EXEC statement, which enables the ATF to start automatically.This parameter does not apply to DBCTL users.



Parameter name*EXEC KI2ATFmp

Default valueN




Panel IDKI256PN

Field Application Trace Facility

Default valueN


Batch parameter nameKI2_CLA_ATFI2

Related parametersv “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_STOR” on page 46v “KI2_CLASSIC_ATF_TRACE” on page 47


KI2_CLASSIC_ATF_ATFBUFFUse the KI2_CLASSIC_ATF_ATFBUFF parameter to specify the number of bytes (in MB) in 64-bitcommon storage that the Application Trace Facility (ATF) uses to buffer the event records. Valid valuesare 1 to 4096. The default value is 4096, where 4096MB = 4GB. The value that you use counts againstMEMLIMIT for your OMEGAMON for IMS (3270) address space.


Location where the parameter value is storedThe KI2ATFmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameATFBUFF=&I2ATFBUC

Default value4096



Panel nameAPPLICATION TRACE FACILITY OPTIONS / RTE: rtename

Panel IDKI256P9

Field ATFBUFF

Default value4096


Batch parameter nameKI2_CLA_ATF_ATFBU

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_STOR” on page 46v “KI2_CLASSIC_ATF_TRACE” on page 47


KI2_CLASSIC_ATF_AUTORESTARTUse the KI2_CLASSIC_ATF_AUTORESTART parameter to activate or deactivate any previously activetraces at startup if those traces have not yet expired.



Parameter nameAUTORESTART=&I2ATFARS

Default valueYES

Permissible valuesYES or NO



Panel IDKI256P9

Field AUTORESTART

Default valueYES


Batch parameter nameKI2_CLA_ATF_ASTRT

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_STOR” on page 46v “KI2_CLASSIC_ATF_TRACE” on page 47


KI2_CLASSIC_ATF_BUFFSIZEUse the KI2_CLASSIC_ATF_BUFFSIZE parameter to specify the number of bytes, in KB, that theApplication Trace Facility (ATF) uses to buffer data to the Journal Logging Facility (JLF).



Parameter nameBUFFSIZE=&I2ATFBUF

Default value32




Panel IDKI256P9

Field BUFFSIZE

Default value32


Batch parameter nameKI2_CLA_ATF_BUFSZ

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_STOR” on page 46v “KI2_CLASSIC_ATF_TRACE” on page 47v


KI2_CLASSIC_ATF_SANDBOXUse the KI2_CLASSIC_ATF_SANDBOX parameter to specify how often Application Trace Facility (ATF)data is to be written to the Journal Logging Facility (JLF). The default setting, OFF, indicates that the tracerecords are to be written when the buffer is full. The ON setting indicates that trace records are to bewritten at the end of each transaction. A number, n , indicates that trace records are to be written every nseconds or when the buffer is full.



Parameter nameSANDBOX=&I2ATFSBX

Default valueOFF

Permissible valuesON, OFF or a value from 1 - 999



Panel IDKI256P9

Field SANDBOX

Default valueOFF

Permissible valuesON, OFF or a value from 1 - 999

Batch parameter nameKI2_CLA_ATF_SBOX

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_STOR” on page 46v “KI2_CLASSIC_ATF_TRACE” on page 47


KI2_CLASSIC_ATF_STORUse the KI2_CLASSIC_ATF_STOR parameter to specify the number of transactions to retain in thememory cache. The Application Trace Facility (ATF) calculates the storage required based on this value.



Parameter nameTOTTRANS=&I2ATFAC

Default value25000




Panel IDKI256P9

Field TOTTRANS

Default value25000


Batch parameter nameKI2_CLA_ATF_STOR

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_TRACE” on page 47


KI2_CLASSIC_ATF_TRACEUse the KI2_CLASSIC_ATF_TRACE parameter to enable Detail tracing, only Exception tracing, or bothDetail and Exception tracing.



Parameter nameTRACE=&I2ATFTRC

Default valueDETAIL

Permissible valuesDETAIL, EXCEPTION, or ALL



Panel IDKI256P9

Field TRACE

Default valueDETAIL

Permissible valuesDETAIL, EXCEPTION, or ALL

Batch parameter nameKI2_CLA_ATF_TRACE

Related parametersv “KI2_CLASSIC_ATFI2” on page 41v “KI2_CLASSIC_ATF_ATFBUFF” on page 42v “KI2_CLASSIC_ATF_AUTORESTART” on page 43v “KI2_CLASSIC_ATF_BUFFSIZE” on page 44v “KI2_CLASSIC_ATF_SANDBOX” on page 45v “KI2_CLASSIC_ATF_STOR” on page 46


KI2_CLASSIC_DEXANUse the KI2_CLASSIC_DEXAN parameter to automatically start DEXAN collection. A value of 'Y'removes the asterisk before the EXEC statement, which enables DEXAN collection to start automatically.Note that this does not apply to DBCTL users.



Parameter name*EXEC KOIDEXmp

Default valueN




Panel IDKI256PN

Field Dexan

Default valueN


Batch parameter nameKI2_CLA_DEXAN


KI2_CLASSIC_EPILOGUse the KI2_CLASSIC_DEXAN parameter to automatically start EPILOG collection. A value of 'Y'removes the asterisk before the EXEC statement, which enables EPILOG collection to start automatically.Note that this does not apply to DBCTL users.



Parameter name*EXEC KEICOLmp

Default valueN




Panel IDKI256PN

Field Epilog

Default valueN


Batch parameter nameKI2_CLA_EPILOG


KI2_CLASSIC_RTAUse the KI2_CLASSIC_RTA parameter to automatically start Response Time Analysis (RTA) collection. Avalue of 'Y' removes the asterisk before the EXEC statement, which enables RTA collection to startautomatically. Note that this does not apply to DBCTL users.



Parameter name*EXEC KRIRTAmp

Default valueN




Panel IDKI256PN

Field RTA

Default valueN


Batch parameter nameKI2_CLA_RTA

Related parametersv “KI2_CLASSIC_RTA_SLOUGH” on page 51v “KI2_CLASSIC_RTA_XCFGROUP” on page 52


KI2_CLASSIC_RTA_SLOUGHUse the KI2_CLASSIC_RTA_SLOUGH parameter to delete unreferenced or incomplete Response TimeAnalysis (RTA) events.


Location where the parameter value is storedThe KRIRTAmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameSTART RTA SLOUGH=&I2RTASLG

Default valueYES



Panel nameSPECIFY RESPONSE TIME ANALYSIS OPTIONS/ RTE: rtename

Panel IDKI256P8

Field SLOUGH OPTION

Default valueYES


Batch parameter nameKI2_CLA_RTA_SLOUGH

Related parametersv “KI2_CLASSIC_RTA” on page 50v “KI2_CLASSIC_RTA_XCFGROUP” on page 52


KI2_CLASSIC_RTA_XCFGROUPUse the KI2_CLASSIC_RTA_XCFGROUP parameter to identify the XCF group name to be used by theResponse Time Analysis (RTA) collection.


Location where the parameter value is storedThe KRIRTAmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameSTART DATACOL XCFGROUP=&I2RTAXGP

Default valueKI2RTASQ

Permissible values


Panel nameSPECIFY RESPONSE TIME ANALYSIS OPTIONS/ RTE: rtename

Panel IDKI256P8

Field XCFGROUP NAME

Default valueKI2RTASQ

Batch parameter nameKI2_CLA_RTA_XCFGROUP

Related parametersv “KI2_CLASSIC_RTA” on page 50v “KI2_CLASSIC_RTA_SLOUGH” on page 51


KI2_CLASSIC_TRFUse the KI2_CLASSIC_TRF parameter to automatically start the Transaction Reporting Facility (TRF). Avalue of 'Y' removes the asterisk before the EXEC statement, which enables the TRF to start automatically.



Parameter name*EXEC KI2TRFmp

Default valueN




Panel IDKI256PN

Field Transaction reporting (TRF)

Default valueN


Batch parameter nameKI2_CLA_TRF

Related parametersv “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_BMPUse the KI2_CLASSIC_TRF_BMP parameter to collect BMP activity information.


Location where the parameter value is storedThe KI2TRFmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameBMP=&I2TRFBMP

Default valueON

Permissible valuesON or OFF


Panel nameSPECIFY TRANSACTION REPORTING FACILITY OPTIONS/ RTE: rtename

Panel IDKI256PT

Field BMP activity data

Default valueON


Batch parameter nameKI2_CLA_TRF_BMP

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_DBDUse the KI2_CLASSIC_TRF_DBD parameter to summarize databases.



Parameter nameDBSUM=&I2TRFDBD

Default valueON




Panel IDKI256PT

Field Summarize databases

Default valueON


Batch parameter nameKI2_CLA_TRF_DBD

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_DB2Use the KI2_CLASSIC_TRF_DB2 parameter to collect DB2® data.



Parameter nameDB2=&I2TRFDB2

Default valueON




Panel IDKI256PT

Field DB2 data

Default valueON


Batch parameter nameKI2_CLA_TRF_DB2

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_DL1Use the KI2_CLASSIC_TRF_DL1 parameter to collect DL/1 database call statistics.



Parameter nameDL1=&I2TRFDL1

Default valueON




Panel IDKI256PT

Field DL/1 data

Default valueON


Batch parameter nameKI2_CLA_TRF_DL1

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_FPUse the KI2_CLASSIC_TRF_FP parameter to collect fast path data.



Parameter nameFP=&I2TRFFP

Default valueOFF




Panel IDKI256PT

Field Fast Path (FP) data

Default valueOFF


Batch parameter nameKI2_CLA_TRF_FP

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_LOG” on page 59v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_LOGUse the KI2_CLASSIC_TRF_LOG parameter to specify where Transaction Reporting Facility (TRF) data iswritten. You can write TRF data to the IMS logs or to the System Management Facility (SMF).



Parameter nameLOG=&I2TRFLOG

Default valueIMS

Permissible valuesIMS or SMF



Panel IDKI256PT

Field Data logs

Default valueIMS

Permissible valuesIMS or SMF

The IMS option writes the TRF data to the IMS logs; the SMF option writes the TRF datato SMF.

Batch parameter nameKI2_CLA_TRF_LOG

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOGREC_ID” on page 60


KI2_CLASSIC_TRF_LOGREC_IDUse the KI2_CLASSIC_TRF_LOGREC_ID parameter to specify a unique IMS or System ManagementFacility (SMF) record ID, which is used by the Transaction Reporting Facility (TRF) to identify logrecords.



Parameter nameRECID=&I2TRFREC

Default value160


Ensure that the value you use is different from record IDs used by other applications,such as EPILOG.



Panel IDKI256PT

Field Log record ID

Default value160


Batch parameter nameKI2_CLA_TRF_LOGREC_ID

Related parametersv “KI2_CLASSIC_TRF” on page 53v “KI2_CLASSIC_TRF_BMP” on page 54v “KI2_CLASSIC_TRF_DBD” on page 55v “KI2_CLASSIC_TRF_DB2” on page 56v “KI2_CLASSIC_TRF_DL1” on page 57v “KI2_CLASSIC_TRF_FP” on page 58v “KI2_CLASSIC_TRF_LOG” on page 59


KI2_CLASSIC_VSAM_MSG_LOGUse the KI2_CLASSIC_VSAM_MSG_LOG parameter to automatically start VSAM message logging. Avalue of 'Y' removes the asterisk before the EXEC statement, which enables VSAM message logging tostart automatically.



Parameter name*EXEC KI2VSMmp

Default valueN




Panel IDKI256PN

Field VSAM message

Default valueN


Batch parameter nameKI2_CLA_VSAM_MSG_LOG


KI2_CLASSIC_RACF_BMP_APPL_GRPUse the KI2_CLASSIC_RACF_BMP_APPL_GRP parameter to specify the RACF® application group nameto associate with the BMP.


Location where the parameter value is storedThe KI2BMPmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameAGN=&I2BMPAGN

Default valueN/A

Permissible valuesA character string no longer than eight characters in length



Panel IDKI256PN

Field RACF application group name for BMP

Default valueN/A

Batch parameter nameKI2_CLA_RACF_BMP_APPL_GRP

Related parametersv “KI2_CLASSIC_RACF_BMP_APPL_GWK” on page 63


KI2_CLASSIC_RACF_BMP_APPL_GWKUse the KI2_CLASSIC_RACF_BMP_APPL_GWK parameter to specify the RACF application group nameto associate with BMPs that generate with multiple Realtime Monitor (RTM) names.


Location where the parameter value is storedThe KI2BMPmp member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameAGN=&I2BMPAGW

Default valueN/A




Panel IDKI256PN

Field RACF application group name for BMP

Default valueN/A


Batch parameter nameKI2_CLA_RACF_BMP_APPL_GWK

Related parametersv “KI2_CLASSIC_RACF_BMP_APPL_GRP” on page 62


KI2_CUA_OMEGCTR_HILEVUse the KI2_CUA_OMEGCTR_HILEV parameter to specify the OMEGACENTER / Gateway high levelqualifier required to create the JCL for the z/OS automation interface exit.


Location where the parameter value is storedThe KI2AOSIM member of the rhilev.midlev.rtename.xKANSAMU library, where x is R, W or I.

Parameter nameDD DISP=SHR,DSN=&I2OGHLEV..TKOGASM

Default valueN/A



Panel nameSPECIFY CUA CONFIGURATION VALUES/ RTE: rtename

Panel IDKI256PP

Field OMEGACENTER hilev - I/CF

Default valueN/A


Batch parameter nameKI2_CUA_OMEGCTR_HILEV


KI2_PSM_ERP_COUNTUse the KI2_PSM_ERP_COUNT parameter to specify the Engine Presentation Space Manager errorrecovery count. The count is the maximum number of simultaneous error recovery options that isallowed for any one physical terminal. Its purpose is to limit the amount of concurrent error recoveryprocesses for a given terminal if the terminal begins to repeatedly send unsolicited input.


Location where the parameter value is storedThe KI2START member of the rhilev.midlev.rtename.xKANCMDU library, where x is R, W or I.

Parameter namePSM ERPCOUNT=&I2PSMERP

Default value10



Panel nameSPECIFY CUA CONFIGURATION VALUES/ RTE: rtename

Panel IDKI256PP

Field TMS:Engine PSM error recovery count

Default value10


Batch parameter nameKI2_PSM_ERP_COUNT


KI2_MIG_HILEVUse the KI2_MIG_VER parameter to specify the high-level qualifier of the runtime environment, whichcontains the older version of OMEGAMON II for IMS that you want to migrate to this version ofOMEGAMON II for IMS.

Required or optionalOptional - required only during migration

Location where the parameter value is storedThe parameter value is not stored, but it is used to create JCL for the migration utility

Parameter nameI2OHILEV

Default valueN/A



Panel nameRUN MIGRATION UTILITY

Panel IDKI256PR4

Field Enter the runtime high-level qualifier you used when you configured your V500 or V510system

Default valueN/A


Batch parameter nameKI2_MIG_HILEV

Related parametersv “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_EPILOG_DSTORIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_EPILOG_DSTOR parameter to specify the data set qualifier and member ofthe Epilog historical datastore lists to migrate to the newer version.



Parameter nameI2OLDEDL

Default valueRKANPAR(KEIEDS)




Panel IDKI256PR4

Field Epilog historical datastore list

Default valueRKANPAR(KEIEDS)


Batch parameter nameKI2_MIG_OLD_EPILOG_DSTOR

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_EPILOG_OPTIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_EPILOG_OPT parameter to specify the data set qualifier and member of theEpilog historical collector options to migrate to the newer version.



Parameter nameI2OLDOPT

Default valueRKANPAR(KEIOPTM0)




Panel IDKI256PR4

Field Epilog historical collector options

Default valueRKANPAR(KEIOPTM0)


Batch parameter nameKI2_MIG_OLD_EPILOG_OPT

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_EPILOG_$DEFIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_EPILOG_$DEF parameter to specify the data set qualifier and member ofthe Epilog default PFKey definition $ definition to migrate to the newer version.



Parameter nameI2O$PDEF

Default valueRKANPAR(KEIDEFLT)




Panel IDKI256PR4

Field Epilog default PFKey definition $

Default valueRKANPAR(KEIDEFLT)


Batch parameter nameKI2_MIG_OLD_EPILOG_$DEF

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_EPILOG_@DEFIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_EPILOG_@DEF parameter to specify the data set qualifier and member ofthe Epilog default PFKey definition @ definition to migrate to the newer version.



Parameter nameI2O@PDEF

Default valueRKANPAR(KEI@DEF)




Panel IDKI256PR4

Field Epilog default PFKey definition @

Default valueRKANPAR(DEI@DEF)


Batch parameter nameKI2_MIG_OLD_EPILOG_@DEF

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_NAMIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_NAM parameter to specify the low-level qualifier of the product-levelsecurity VSAM cluster to migrate to the newer version.



Parameter nameI2OLDNAM

Default valueRKI2NAM




Panel IDKI256PR4

Field Product-level security (VSAM)

Default valueRKI2NAM


Batch parameter nameKI2_MIG_OLD_NAM

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_PROFIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_PROF parameter to specify the data set qualifier of the profiles andexception thresholds to migrate to the newer version.



Parameter nameI2O$PFSV

Default valueRKOIPFSV




Panel IDKI256PR4

Field Profiles and exception thresholds

Default valueRKOIPFSV


Batch parameter nameKI2_MIG_OLD_PROF

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_SCRN_SPCIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_SCRN_SPC parameter to specify the data set qualifier of the screen spacesand menus to migrate to the newer version.



Parameter nameI2O$PCSV

Default valueRKOIPCSV




Panel IDKI256PR4

Field Screen spaces and menus

Default valueRKOIPCSV


Batch parameter nameKI2_MIG_OLD_SCRN_SPC

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_TDB” on page 74v “KI2_MIG_VER” on page 75


KI2_MIG_OLD_TDBIf you are migrating from OMEGAMON II for IMS V500 or V510 to this version of OMEGAMON II forIMS, use the KI2_MIG_OLD_TDB parameter to specify the low-level qualifier of the internal tablesdatabase VSAM cluster to migrate to the newer version.



Parameter nameI2OLDTB

Default valueRKI2TDB




Panel IDKI256PR4

Field Internal tables database (VSAM)

Default valueRKI2TDB


Batch parameter nameKI2_MIG_OLD_TDB

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_VER” on page 75


KI2_MIG_VERUse the KI2_MIG_VER parameter to specify the version number, in nnn format, of the OMEGAMON IIfor IMS from which you are migrating.



Parameter name&I2MIGVER

Default valueN/A

Permissible valuesCharacter string no longer than three characters in length



Panel IDKI256PR

Field Enter previous OMEGAMON II for IMS version

Default valueN/A

Permissible valuesCharacter string no longer than three characters in length

Batch parameter nameKI2_MIG_VER

Related parametersv “KI2_MIG_HILEV” on page 66v “KI2_MIG_OLD_EPILOG_DSTOR” on page 67v “KI2_MIG_OLD_EPILOG_OPT” on page 68v “KI2_MIG_OLD_EPILOG_$DEF” on page 69v “KI2_MIG_OLD_EPILOG_@DEF” on page 70v “KI2_MIG_OLD_NAM” on page 71v “KI2_MIG_OLD_PROF” on page 72v “KI2_MIG_OLD_SCRN_SPC” on page 73v “KI2_MIG_OLD_TDB” on page 74


KI2_X_IMS_CONFIRM_SHUTDOWNUse the KI2_X_IMS_CONFIRM_SHUTDOWN parameter to terminate the OMEGAMON II for IMS onz/OS address space. You can specify the maximum number of seconds between two successiveSHUTDOWN commands or between two successive MVS™ STOP (P) commands.



Parameter nameCONFIRM(&XI2FIRM)

Default value0


The CONFIRM(0) parameter allows the TMS:Engine to shut down immediately withoutrequiring an additional, confirming SHUTDOWN command. The CONFIRM(n) parameterprevents accidental shutdowns by requiring you to re-enter the command within thespecified number of seconds. For example, CONFIRM(15) requires you to enterSHUTDOWN twice within 15 seconds to terminate the address space.

In the Configuration Tool (ICAT)This value cannot be defined using the Configuration Tool.

Related parametersv “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_DEBUG_TRACEDo not modify this parameter except under the guidance of IBM Software Support. This parameteractivates the TMS:Engine debugging services.



Parameter nameDEBUG(&KI2DEBG)

Default valueN

Permissible valuesY or Nv The N value specifies to record basic debugging information.v The Y value specifies not to record basic debugging information.

Note: The DEBUG and STGDEBUG parameters may affect each other. If you specifyDEBUG(Y) and omit STGDEBUG, you activate basic storage debugging and can cause anincrease in storage use parameters. For proper use, specify STGDEBUG after DEBUG inthe initialization deck; DEBUG overrides STGDEBUG if it follows STGDEBUG.


Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_LGSA_VERIFYDo not modify this parameter except under the guidance of IBM Software Support. This parameterinvokes the TMS:Engine to check that the $GSA address is available.



Parameter nameLGSA(&XI2LGSA)

Default valueY

Permissible valuesY or Nv The Y value invokes the TMS:Engine to check that the $GSA address is available.v The N value specifies not to check that the $GSA address is available.


Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_LOGBLOCK_SIZEDo not modify this parameter except under the guidance of IBM Software Support. This commandspecifies the size of each BSAM buffer to be allocated for RKLVLOG processing. The syntax isLOGBLOCK(nnnnn) where n is the size of the RKLVLOG buffers in bytes.



Parameter nameLOGBLOCK(&XI2LGBLK)

Default value160



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_LSRPOOL_BUFFER_NUM1Use the KI2_X_IMS_LSRPOOL_BUFFER_NUM1 parameter to specify the number of virtual storagebuffers to be allocated for buffer pool 1 in the VSAM resource pool. You must individually specify a sizefor each buffer pool; you cannot string the definitions. Use this syntax to specify the buffer size and thenumber of buffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)



Parameter nameLSRPOOL(&XI2BSZ1, &XI2NBF1)

Default value3



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_LSRPOOL_BUFFER_NUM2Use the KI2_X_IMS_LSRPOOL_BUFFER_NUM2 parameter to specify the size (in bytes) of the virtualstorage buffer in buffer pool 2 in the VSAM resource pool. You must individually specify a size for eachbuffer pool; you cannot string the definitions. Use this syntax to specify the buffer size and the number ofbuffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)




Default value32





KI2_X_IMS_LSRPOOL_BUFFER_NUM3Use the KI2_X_IMS_LSRPOOL_BUFFER_NUM3 parameter to specify the number of virtual storagebuffers to be allocated for buffer pool 3 in the VSAM resource pool. You must individually specify a sizefor each buffer pool; you cannot string the definitions. Use this syntax to specify the buffer size and thenumber of buffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)




Default value8





KI2_X_IMS_LSRPOOL_BUFSIZE1Use the KI2_X_IMS_LSRPOOL_BUFSIZE1 parameter to specify the size, in bytes, of the virtual storagebuffer in buffer pool 1 in the VSAM resource pool. You must individually specify a size for each bufferpool; you cannot string the definitions. Use this syntax to specify the buffer size and the number ofbuffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)




Default value32768

Permissible values512, 1024, 2048, 8192, 12288, 16384, 20480, 24576, 28672, or 32768


Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93






Default value4096









Default value2048





KI2_X_IMS_SDUMP_SVC_SYS1_DUMPDo not modify this parameter except under the guidance of IBM Software Support. This commandgenerates SVC dumps.


Location where the parameter value is storedThe KI2SYSIN member of the rhilev.midlev.rtename.xKANPARU library and the &I2CUAPRCmember of the rhilev.midlev.rtename.xKANSAMU library, where x is R, W or I.

Parameter namePARM='SDUMP(&XI2BSVC)'

Default valueN

Permissible valuesY, N, S, or Mv The Y parameter value directs the SVC dump to a system dump data set

(SYS1.DUMPxx). Before you specify the Y value, ensure that the TMS:Engine job step isAPF-authorized and that the SYS1.DUMPxx data sets are large enough to contain thecontents of the TMS:Engine address space.

v The N parameter value directs formatted dumps to the RKLVSNAP data set. Ifpossible, avoid formatted dumps because these types of dumps disable the TMS:Engineaddress space for a longer time than either SVC dumps or SYSMDUMPs, and are moredifficult to analyze.

v The S parameter value directs summary dumps to the RKLVSNAP data set. Asummary dump consists of an ABEND summary and dispatcher summary and doesnot provide enough information for reliable problem analysis. Use this setting forspecific testing purposes only.

v The M parameter value directs ABEND dumps to the data set with the SYSMDUMPDD name. This type of dump is not formatted by the operating system and must beanalyzed with IPCS. Only the first dump taken is captured in the SYSMDUMP datasetunless JCL specifies DISP=MOD. The TMS:Engine automatically initializes theSYSMDUMP data set with an end-of-file mark.


Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_STORAGE_LIMIT_EXTENDUse the KI2_X_IMS_STORAGE_LIMIT_EXTEND parameter to specify the maximum size for theTMS:Engine extended storage (above-the-line) request.



Parameter nameLIMIT(&XI2ELIM, X)

Default value23


The maximum extended storage request size is specified as a power of 2. The minimumextended storage size is 16, which specifies a limit of 64K. The maximum is 25, whichspecifies a limit of 32M.


Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_STORAGE_LIMIT_PRIMARYUse the KI2_X_IMS_STORAGE_LIMIT_PRIMARY parameter to specify the maximum size for theTMS:Engine primary storage request.



Parameter nameLIMIT(&XI2PLIM, P)

Default value16


The maximum primary storage request size is specified as a power of 2. The minimumprimary storage size is 16, which specifies a limit of 64K. The maximum is 25, whichspecifies a limit of 32M.




KI2_X_IMS_STORAGE_MIN_EXTENDUse the KI2_X_IMS_STORAGE_MIN_EXTEND parameter to specify the minimum amount, in kilobytes,of extended storage to be allocated. Extended storage is above the 16-megabyte line. To use extendedstorage, you must code a non-zero value for the minimum parameter below the 16-megabyte line.



Parameter nameMINIMUM(&XI2EMIN, X)

Default value20000



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_STORAGE_MIN_PRIMARYUse the KI2_X_IMS_STORAGE_MIN_PRIMARY parameter to specify the minimum amount, in kilobytes,of primary storage to be allocated. Primary storage is below the 16-megabyte line. To use extendedstorage, you must code a value greater than zero for the minimum parameter below the 16-megabyteline.



Parameter nameMINIMUM(&XI2PMIN, P)

Default value4096





KI2_X_IMS_STORAGE_RESERVE_EXTUse the KI2_X_IMS_STORAGE_RESERVE_EXT parameter to specify the number of kilobytes of extended(above-the-line) storage to reserve for other routines that might perform their own GETMAINs in thisaddress space. If your RESERVE value is too small, you might encounter IST566I messages from VTAMor S80A, S878, S066, S40D, or S0F9 abends.



Parameter nameRESERVE(&XI2ERES, X)

Default value2048



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_RESERVE_PRI” on page 92v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_STORAGE_RESERVE_PRIUse the KI2_X_IMS_STORAGE_RESERVE_PRI parameter to specify the number of kilobytes of primary(below-the-line) storage to reserve for other routines (for example, ACF2 and RACF) that might performtheir own GETMAINs in this address space. The ACF2 and RACF routines use approximately 1K ofprimary storage per logged-on user. If your RESERVE value is too small, you might encounter IST566Imessages from VTAM or S80A, S878, S066, S40D, or S0F9 abends.



Parameter nameRESERVE(&XI2PRES, P)

Default value2048



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_RESERVE_EXT” on page 91v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93


KI2_X_IMS_STORAGE_STGDEBUGUse this parameter to activate TMS:Engine storage debugging services.



Parameter nameSTGDEBUG(&XI2STDB)

Default valueN

Permissible valuesY, N or Xv The Y value specifies to record basic storage debugging information.v The N parameter value specifies not to record basic storage debugging information.v The X value specifies to record extended storage debugging information.



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_LIMIT_PRIMARY” on page 88


KI2_X_SECURITY_RESOURCE_CLASSUse the KI2_X_SECURITY_RESOURCE_CLASS parameter to specify a member in RKANPARU thatcontains protected class lists information. External security packages use this parameter to construct thecorrect resource validation request.


Location where the parameter value is storedThe KI2INNAM member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameCLASSES=&XI2SCLA

Default value(blank)



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89“KI2_X_IMS_STORAGE_STGDEBUG” on

page 93


KI2_X_SECURITY_USER_EXITUse the KI2_X_SECURITY_USER_EXIT parameter to specify a load module name for an exit routine thatcauses validation to run.


Location where the parameter value is storedThe KI2INNAM member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameEXIT=&XI2SUEX

Default value(blank)



Related parametersv “KI2_X_IMS_CONFIRM_SHUTDOWN” on page 76v “KI2_X_IMS_DEBUG_TRACE” on page 77v “KI2_X_IMS_LGSA_VERIFY” on page 78v “KI2_X_IMS_LSRPOOL_BUFFER_NUM1” on page 80v “KI2_X_IMS_LSRPOOL_BUFFER_NUM2” on page 81v “KI2_X_IMS_LSRPOOL_BUFFER_NUM3” on page 82v “KI2_X_IMS_LSRPOOL_BUFSIZE1” on page 83v “KI2_X_IMS_LSRPOOL_BUFSIZE2” on page 84v “KI2_X_IMS_LSRPOOL_BUFSIZE3” on page 85v “KI2_X_IMS_SDUMP_SVC_SYS1_DUMP” on page 86v “KI2_X_IMS_STORAGE_LIMIT_EXTEND” on page 87v “KI2_X_IMS_STORAGE_MIN_EXTEND” on page 89v “KI2_X_IMS_STORAGE_STGDEBUG” on page 93v “KI2_X_SECURITY_RESOURCE_CLASS” on page 94


KI2_X_STC_INCLUDE_IMSMON_FLAGDo not modify this parameter except under the guidance of IBM Software Support. This parameterconfigures the Application Trace Facility option or the Attach Command BMP option, or both. If you setthe Y parameter value, it includes the appropriate data definition for the IMS RESLIB in the IMS controlregion of the generated JCL job.


Location where the parameter value is storedThe parameter value is not stored, but it is used to create the JCL job.

Parameter name&XI2IMSMN

Default valueN





Chapter 3. KI5 configuration parameters

The configuration parameters for the OMEGAMON XE for IMS on z/OS monitoring agent are groupedlogically in the configuration file.

This section provides an overview of the parameters found in the OMEGAMON XE for IMS on z/OSsection of the PARMGEN configuration profile. The prefix associated with OMEGAMON XE for IMS onz/OS is KI5.

The following parameters are classified in the order in which the parameters exist in PARMGEN.v IMS and IRLM subsystem information table

– “KI5_II” on page 99– “KI5_IInn_ROW” on page 100– “KI5_IInn_SSID” on page 101– “KI5_IInn_SS_AUTO” on page 102– “KI5_IInn_SS_CONFLICT” on page 103– “KI5_IInn_SS_COUPFAC” on page 104– “KI5_IInn_SS_DBCMSK” on page 105– “KI5_IInn_SS_DBCTHR” on page 106– “KI5_IInn_SS_DEX” on page 107– “KI5_IInn_SS_DSHR” on page 108– “KI5_IInn_SS_ENV” on page 109– “KI5_IInn_SS_HADB” on page 110– “KI5_IInn_SS_HLTH” on page 111– “KI5_IInn_SS_LCK” on page 112– “KI5_IInn_SS_MQSTAT” on page 113– “KI5_IInn_SS_MSC” on page 114– “KI5_IInn_SS_OSAM” on page 115– “KI5_IInn_SS_OTMA” on page 116– “KI5_IInn_SS_PARM” on page 117– “KI5_IInn_SS_POOLS” on page 118– “KI5_IInn_SS_RESOURCE” on page 119– “KI5_IInn_SS_RGO” on page 120– “KI5_IInn_SS_RTAETE” on page 121– “KI5_IInn_SS_RTAEXCP” on page 122– “KI5_IInn_SS_RTAGRPH” on page 123– “KI5_IInn_SS_RTAINTV” on page 124– “KI5_IInn_SS_RTARMON” on page 125– “KI5_IInn_SS_RTASLOT” on page 126– “KI5_IInn_SS_SHRQ” on page 127– “KI5_IInn_SS_TYP” on page 128– “KI5_IInn_SS_WORK” on page 129– “KI5_IInn_SS_ICMD” on page 130

v IMS Connect settings– “KI5_COMP” on page 131– “KI5_COMPnn_ICON_NAME” on page 132– “KI5_COMPnn_ROW” on page 133– “KI5_COMPnn_TYPE” on page 134– “KI5_ICT_AUTODISCOVER” on page 135– “KI5_ICT_BUFFER_SIZE” on page 136– “KI5_ICT_BUFFER_THRESH” on page 137– “KI5_ICT_COLLECT_INTERVAL” on page 138


– “KI5_ICT_COLLECT_LEVEL” on page 139– “KI5_ICT_MESSAGE_LEVEL” on page 140– “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141

v Additional OMEGAMON XE for IMS agent settings– “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142– “KI5_X_AGT_DEBUG_TRACE” on page 143– “KI5_X_AGT_KDC_DEBUG” on page 144– “KI5_X_AGT_LGSA_VERIFY” on page 145– “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146– “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147– “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148– “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149– “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150– “KI5_X_AGT_STORAGE_RESERVE_EXT” on page 151– “KI5_X_AGT_STORAGE_RESERVE_PRI” on page 152– “KI5_X_AGT_STORAGE_STGDEBUG” on page 153– “KI5_X_AGT_TASKS_ATTACHED_NUM” on page 154


KI5_IIUse the KI5_II parameter to specify the beginning or end of the subsystem information for the IMS andInternal Resource Lock Manager (IRLM) subsystems, which are monitored by the OMEGAMON XE forIMS product. If the variable value is BEGIN, the variables up to either the next BEGIN or the next ENDcontain all the information necessary to construct information for each subsystem. The END valueindicates the end of the subsystem information.


Location where the parameter value is storedThis value is not stored, but it is used for internal processing

Parameter name

Default valueBEGIN



Related parametersAll KI5_IInn_* parameters


KI5_IInn_ROWUse the KI5_IInn_ROW parameter to specify the beginning or end of a single group for the monitoringproduct. If the variable value is BEGIN, the variables up to either the next BEGIN or the next ENDcontain all the information necessary to construct the group information for a single group.



Parameter name

Default valueBEGIN





KI5_IInn_SSIDUse the KI5_IInn_SSID parameter to specify the IMSID of the IMS subsystem to be monitored. You setthe IMSID on the IMSGEN macro at IMS system definition time.


Location where the parameter value is storedThe KIPCNFG member of the rhilev.midlev.rtename.xKANPARU library where x is R, W or I.

Parameter nameIMS(&KIPSSNM) or IRLM(&KIPSSNM)

Default valueN/A



Panel nameIMS SUBSYSTEMS MONITORED / RTE: rtename

Panel IDKI541P2

Field IMS Name

Default valueN/A




KI5_IInn_SS_AUTOUse the KI5_IInn_SS_AUTO parameter to specify the status of the IMS autodiscovery row. If thesubsystem that you add contains a wildcard “*”, this value is set to Y.



Parameter name&KIPAUTOD

Default value


In the Configuration Tool (ICAT)This parameter cannot be set using the Configuration Tool



KI5_IInn_SS_CONFLICTUse the KI5_IInn_SS_CONFLICT parameter to collect data for Internal Resource Lock Manager (IRLM)global locks.


Location where the parameter value is storedThe KIPCNFG member of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameCONFLICT(&KIPSINT1)

Default valueON



Panel nameSPECIFY IMS DATA COLLECTOR OPTIONS / RTE: rtename

Panel IDKI541P5

Field IRLM Global Locks Statistics

Default valueON




KI5_IInn_SS_COUPFACUse the KI5_IInn_SS_COUPFAC parameter to collect data for the coupling facility.



Parameter nameCOUPFAC(&KIPSPRMQ)

Default valueON



Panel nameSPECIFY IMS DATA COLLECTOR OPTIONS (1 OF 2)

Panel IDKI541P3

Field (COUP) Coupling Facility statistics

Default valueON




KI5_IInn_SS_DBCMSKUse the KI5_IInn_SS_DBCMSK parameter to display sensitive data from the Program Control Block (PCB)key fields, segment search argument (SSA), and Input/Output Areas (IOAREA).



Parameter nameMASKDATA(&KIPSPRMB)

Default valueN


If you set the value to Y, asterisks (*) overlay the PCB key fields, SSA and IOAREA in thedisplay. If you set the value to N, the areas display the value retained in memory, in bothcharacter and hexadecimal formats.



Panel IDKI541P3

Field (SENS) Sensitive Data Screen

Default valueN




KI5_IInn_SS_DBCTHRUse the KI5_IInn_SS_DBCTHR parameter to collect data pertaining to DBCTL threads.



Parameter nameDBCTHRDS(&KIPSPRMA)

Default valueON




Panel IDKI541P3

Field (DBCT) DBCTL thread statistics

Default valueON




KI5_IInn_SS_DEXUse the KI5_IInn_SS_DEX parameter to collect data pertaining to DEXAN, that is, bottleneck analysis.



Parameter nameDEXAN(&KIPSPRMF)

Default valueON




Panel IDKI541P3

Field (DEXAN) Bottleneck analysis (DEXAN) data

Default valueON




KI5_IInn_SS_DSHRUse the KI5_IInn_SS_DSHR parameter to collect coupling facility statistics related to the VSAM andOSAM cache structures.



Parameter nameDATASHAR(&KIPSIN3Y)

Default valueON




Panel IDKI541P3

Field (DSHR) VSAM cache statistics

Default valueON




KI5_IInn_SS_ENVUse the KI5_IInn_SS_ENV parameter to collect data pertaining to IMS address spaces, regions, fast path,and external subsystems.



Parameter nameIMSENV(&KIPSPRM7)

Default valueON




Panel IDKI541P3

Field (IENV) Environment data (address spaces, regions, fast path, external subsystems)

Default valueON




KI5_IInn_SS_HADBUse the KI5_IInn_SS_HADB parameter to collect data pertaining to HALDB.



Parameter nameHALDB(&KIPSPRMD)

Default valueON




Panel IDKI541P3

Field (HALDB) HALDB information

Default valueON




KI5_IInn_SS_HLTHUse the KI5_IInn_SS_HLTH parameter to collect data pertaining to the health of an IMS system.



Parameter nameHEALTH(&KIPSPRMP)

Default valueON




Panel IDKI541P3

Field (HLTH) Health information

Default valueON




KI5_IInn_SS_LCKUse the KI5_IInn_SS_LCK parameter to collect data pertaining to local Program Isolation (PI) or InternalResource Lock Manager (IRLM) locks.



Parameter nameLCLLOCKS(&KIPSPRMH)

Default valueON




Panel IDKI541P3

Field (LCK) Local PI/IRLM lock data

Default valueON




KI5_IInn_SS_MQSTATUse the KI5_IInn_SS_MQSTAT parameter to collect data for MQ external subsystems.



Parameter nameMQSTAT(&KIPSINT2)

Default valueON




Panel IDKI541P3

Field (MQST) MQ subsystem information

Default valueON




KI5_IInn_SS_MSCUse the KI5_IInn_SS_MSC parameter to collect data about Multiple Systems Coupling (MSC) links andqueues.



Parameter nameMSC(&KIPSIN2Y)

Default valueON




Panel IDKI541P3

Field (MSC) Multiple Systems Coupling statistics

Default valueON




KI5_IInn_SS_OSAMUse the KI5_IInn_SS_OSAM parameter to collect coupling facility statistics related to the OSAM cachestructure.



Parameter nameOSAMSHAR(&KIPSINT3)

Default valueON




Panel IDKI541P3

Field (OSAM) OSAM cache statistics

Default valueON




KI5_IInn_SS_OTMAUse the KI5_IInn_SS_OTMA parameter to collect data pertaining to OTMA.



Parameter nameOTMA(&KIPSPRME)

Default valueON




Panel IDKI541P3A

Field (OTMA) OTMA statistics

Default valueON




KI5_IInn_SS_PARMUse the KI5_IInn_SS_PARM parameter to collect data for IMS startup parameters.



Parameter nameIMSPARMS(&KIPSPRM6)

Default valueON




Panel IDKI541P3

Field (IMSP) IMS startup parameter data

Default valueON




KI5_IInn_SS_POOLSUse the KI5_IInn_SS_POOLS parameter to collect statistics for communication, database and programpools.



Parameter namePOOLS(&KIPSINT4)

Default valueON




Panel IDKI541P3A

Field (SUBP) Communication, database, program pools

Default valueON




KI5_IInn_SS_RESOURCEUse the KI5_IInn_SS_RESOURCE parameter to collect IMS resource data such as device I/O and logging.



Parameter nameRESOURCE(&KIPSIN4Y)

Default valueON




Panel IDKI541P3

Field (COMP) Resource data (device I/O, logging)

Default valueON




KI5_IInn_SS_RGOUse the KI5_IInn_SS_RGO parameter to collect data pertaining to region occupancy.



Parameter nameREGOCCUP(&KIPSPRMO)

Default valueON




Panel IDKI541P3A

Field (RGO) Region Occupancy

Default valueON




KI5_IInn_SS_RTAETEUse the KI5_IInn_SS_RTAETE parameter to collect Response Time Analysis (RTA) data pertaining to theworst performing transactions and Logical Terminals (LTERM).



Parameter nameRTAETE(&KIPSPRMN)

Default valueON




Panel IDKI541P3A

Field (RTAE) RTA End-to-End statistics

Default valueON




KI5_IInn_SS_RTAEXCPUse the KI5_IInn_SS_RTAEXCP parameter to collect Response Time Analysis exception data.



Parameter nameRTAEXCP(&KIPSPRMM)

Default valueON




Panel IDKI541P3A

Field (RTAX) RTA Exception data

Default valueON




KI5_IInn_SS_RTAGRPHUse the KI5_IInn_SS_RTAGRPH parameter to collect Response Time Analysis (RTA) short-term graphicaldata.



Parameter nameRTAGRPH(&KIPSPRMK)

Default valueON




Panel IDKI541P3A

Field (RTAG) RTA Short term graphical data

Default valueON




KI5_IInn_SS_RTAINTVUse the KI5_IInn_SS_RTAINTV parameter to collect Response Time Analysis (RTA) interval data.



Parameter nameRTAINTV(&KIPSPRMI)

Default valueON




Panel IDKI541P3A

Field (RTAI) RTA Interval statistics

Default valueON




KI5_IInn_SS_RTARMONUse the KI5_IInn_SS_RTARMON parameter to collect Response Time Analysis (RTA) data pertaining tothe worst performing transactions and Logical Terminals (LTERM).



Parameter nameRTARMON(&KIPSPRML)

Default valueON




Panel IDKI541P3A

Field (RTAR) RTA Worst response times

Default valueON




KI5_IInn_SS_RTASLOTUse the KI5_IInn_SS_RTASLOT parameter to collect data pertaining to the Response Time Analysis (RTA)time-of-day slot.



Parameter nameRTASLOT(&KIPSPRMJ)

Default valueON




Panel IDKI541P3A

Field (RTAS) RTA Time-of-day slot data

Default valueON




KI5_IInn_SS_SHRQUse the KI5_IInn_SS_SHRQ parameter to collect data from shared queues.



Parameter nameSHAREDQ(&KIPSPRM5)

Default valueON




Panel IDKI541P3A

Field (SHRQ) Shared queue statistics

Default valueON




KI5_IInn_SS_TYPUse the KI5_IInn_SS_TYP parameter to specify the type of subsystem used by the OMEGAMON XE forIMS product.


Location where the parameter value is storedThe KIPSTART member of the rhilev.midlev.rtename.xKANCMDU library and the KIPCNFGmember of the rhilev.midlev.rtename.xKANPARU library, where x is R, W or I.

Parameter nameKIPSTART: IPDC &KIPSSTYP(&KIPSSNM)

KIPCNFG: &KIPSSTYP(&KIPSSNM)

Default valueSERVER

Permissible valuesSERVER, IMS, or IRLM

There are 3 types of subsystem:v SERVER – this is an internal subsystem type that is used exclusively by the Tivoli

Enterprise Monitoring Server. Do not specify the value for this field; the configurationwill set the value for you.

v IMS – indicates that this subsystem is an IMS subsystemv IRLM – indicates that this subsystem is an IRLM subsystem


Panel nameTo set this value, select option 1 (Define IMS subsystems) or option 2 (Define IRLMsubsystems) on this panel: CONFIGURE IBM TIVOLI OMEGAMON XE FOR IMS ONZ/OS / RTE: rtename



KI5_IInn_SS_WORKUse the KI5_IInn_SS_WORK parameter to collect data pertaining to IMS transactions, ProgramScheduling Blocks (PSB), and Logical Terminals (LTERM).



Parameter nameWORKLOAD(&KIPSPRM8)

Default valueON




Panel IDKI541P3A

Field (WORK) Workload (transactions, PSBs LTERMs)

Default valueON




KI5_IInn_SS_ICMDUse the KI5_IInn_SS_ICMD parameter to specify support for IMS commands.



Parameter nameICMD(&KIPSICMD)

Default valueON




Panel IDKI541P3

Field (ICMD)IMS command interface

Default valueON




KI5_COMPUse the KI5_COMP parameter to configure an OTMA connection. If the variable value is BEGIN, thevariables up to either the next BEGIN or the next END contain all the information necessary to constructinformation for each subsystem. The END value indicates the end of the subsystem information.



Parameter name

Default valueBEGIN



Related parametersv “KI5_COMPnn_ICON_NAME” on page 132v “KI5_COMPnn_ROW” on page 133v “KI5_COMPnn_TYPE” on page 134


KI5_COMPnn_ICON_NAMEUse the KI5_COMPnn_ICON_NAME parameter to specify the user-defined name of the IMS Connectaddress space, that is, the job to be monitored.


Location where the parameter value is storedThe KIPICTP member of the rhilev.midlev.rtename.xKANPARU library where x is R, W or I.

Parameter nameICT_INCLUDE=(&KIPCONAM)

Default valueN/A



Panel nameSPECIFY THE IMS CONNECT JOB NAME TO MONITOR/ RTE: rtename

Panel IDKI541PO5

Field IMS Connect Job Name

Default valueN/A


Related parametersv “KI5_COMP” on page 131v “KI5_COMPnn_ROW” on page 133v “KI5_COMPnn_TYPE” on page 134


KI5_COMPnn_ROWUse the KI5_COMPnn_ROW parameter to specify the beginning or end of a single group for themonitoring product. If the variable value is BEGIN, the variables up to either the next BEGIN or the nextEND contain all the information necessary to construct the group information for a single group.



Parameter name

Default valueBEGIN



Related parametersv “KI5_COMP” on page 131v “KI5_COMPnn_ICON_NAME” on page 132v “KI5_COMPnn_TYPE” on page 134


KI5_COMPnn_TYPEThe KI5_COMPnn_TYPE parameter is a type of table entry.



Parameter nameKIPOTTYP

Default value

Permissible values* or ICON


Related parametersv “KI5_COMP” on page 131v “KI5_COMPnn_ICON_NAME” on page 132v “KI5_COMPnn_ROW” on page 133


KI5_ICT_AUTODISCOVERUse the KI5_ICT_AUTODISCOVER parameter to enable the auto-discovery of IMS Connect addressspaces for which names have been specified and extensions enabled. If you do not enable auto-discovery,you must use Take Action commands from the Tivoli Enterprise Portal to connect to an IMS Connectaddress space.



Parameter nameICT_AUTODISCOVER = &KI5ICTAD

Default valueYES



Panel nameJOB NAMES OF MONITORED IMS CONNECTS / RTE: rtename

Panel IDKI541PO4

Field Auto Discovery

Default valueYES


Batch parameter nameKI5_ICT_AD

Related parametersv “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_ICT_MESSAGE_LEVEL” on page 140v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_ICT_BUFFER_SIZEUse the KI5_ICT_BUFFER_SIZE parameter to specify the buffer size in which to collect IMS Connect data.In addition to the Buffer Threshold parameter, these values determine the frequency of buffer writes fromIMS Connect to the collector.



Parameter nameICT_BUFFER_SIZE = &KI5ICTBS

Default value12




Panel IDKI541PO4

Field Buffer Size (in K)

Default value12


Batch parameter nameKI5_ICT_BS

Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_ICT_MESSAGE_LEVEL” on page 140v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_ICT_BUFFER_THRESHUse the KI5_ICT_BUFFER_THRESH parameter to specify a fill percentage for the buffer at which the IMSConnect is to write data to the collector. In addition to the Buffer Size parameter, these values determinethe frequency of buffer writes from the IMS Connect to the collector.



Parameter nameICT_BUFFER_THRESH = &KI5ICTBT

Default value85




Panel IDKI541PO4

Field Buffer Threshold Pct

Default value85


Batch parameter nameKI5_ICT_BT

Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_ICT_MESSAGE_LEVEL” on page 140v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_ICT_COLLECT_INTERVALUse the KI5_ICT_COLLECT_INTERVAL parameter to specify the collection time, in minutes, for IMSConnect statistics.



Parameter nameICT_COLLECT_INTERVAL = &KI5ICTCI

Default value15

Permissible values5-60



Panel IDKI541PO4

Field Collection Interval

Default value15


Batch parameter nameKI5_ICT_CI

Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_ICT_MESSAGE_LEVEL” on page 140v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_ICT_COLLECT_LEVELUse the KI5_ICT_COLLECT_LEVEL parameter to specify the collection level. If you increase thecollection level, more data is collected.



Parameter nameICT_COLLECT_LEVEL = &KI5ICTCL

Default value4




Panel IDKI541PO4

Field Collection Level

Default value4


Batch parameter nameKI5_ICT_CL

Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_MESSAGE_LEVEL” on page 140v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_ICT_MESSAGE_LEVELUse the KI5_ICT_MESSAGE_LEVEL parameter to specify the volume of message traffic that the collectorissues to the system console.



Parameter nameICT_MESSAGE_LEVEL = &KI5ICTML

Default valueERROR

Permissible valuesERROR, VERBOSE, or DEBUG



Panel IDKI541PO4

Field Message Level

Default valueERROR

Permissible valuesERROR, VERBOSE, or DEBUG

Batch parameter nameKI5_ICT_ML

Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_X_ICT_IMS_CONNECT_FLAG” on page 141


KI5_X_ICT_IMS_CONNECT_FLAGUse the KI5_X_ICT_IMS_CONNECT_FLAG parameter to enable IMS Connect functionality. You must setthe KI5_X_ICT_IMS_CONNECT_FLAG parameter to Y to use the SCEXLINK and SFUNLINK data sets. Ifthis parameter is disabled (N), you cannot specify the data set definition statements for these data sets.


Location where the parameter value is storedThe parameter value is not stored; it is only used to determine the outcome of a decisionstatement within PARMGEN that enables or disables the use of IMS Connect.

Parameter name

Default valueN



Related parametersv “KI5_ICT_AUTODISCOVER” on page 135v “KI5_ICT_BUFFER_SIZE” on page 136v “KI5_ICT_BUFFER_THRESH” on page 137v “KI5_ICT_COLLECT_INTERVAL” on page 138v “KI5_ICT_COLLECT_LEVEL” on page 139v “KI5_ICT_MESSAGE_LEVEL” on page 140


KI5_X_AGT_CONFIRM_SHUTDOWNUse the KI5_X_AGT_CONFIRM_SHUTDOWN parameter to terminate the OMEGAMON XE for IMS onz/OS address space. You can specify the maximum number of seconds between two successiveSHUTDOWN commands or between MVS STOP (P) commands.


Location where the parameter value is storedThe KI5SYSIN member of the rhilev.midlev.rtename.xKANPARU library where x is R, W or I.

Parameter nameCONFIRM(&XI5FIRM)

Default value0


The CONFIRM(0) parameter allows the TMS:Engine to shut down immediately withoutrequiring an additional, confirming SHUTDOWN command. The CONFIRM(n) parameterprevents accidental shutdowns by requiring you to re-enter the command within thespecified number of seconds. For example, CONFIRM(15) requires you to enterSHUTDOWN twice within 15 seconds to terminate the address space.


Related parametersv “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_DEBUG_TRACEDo not modify this parameter except under the guidance of IBM Software Support. This parameteractivates the TMS:Engine debugging services.



Parameter nameDEBUG(&XI5DEBG)

Default valueN

Permissible valuesY or Nv The N value specifies to record basic debugging information.v The Y value specifies not to record basic debugging information.



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_KDC_DEBUGDo not modify this parameter except under the guidance of IBM Software Support. This parameter isintended for stable applications in production.


Location where the parameter value is storedThe KI5ENV member of the rhilev.midlev.rtename.xKANPARU library where x is R, W or I.

Parameter nameKDC_DEBUG=&XI5DBUG

Default valueN

Permissible valuesY, N, D, M or A

Set this parameter to Y if you want KDC_DEBUG=Y to be the override setting in theRKANPARU(KI5ENV) member. Otherwise, the default setting of KDC_DEBUG=N isused. This default parameter instructs the data communications layer to reportcommunications problems using a minimal, summary format.

The default KDC_DEBUG=N generates standard RAS1 trace data in the Agent RKLVLOGin addition to the summary information used for diagnosing possible timeout conditions.The following settings provide information about data communications problems:v KDC_DEBUG=N: minimal tracing (default)v KDC_DEBUG=Y: full-packet tracingv KDC_DEBUG=D: KDC_DEBUG=Y plus STATE & FLOW tracingv KDC_DEBUG=M: KDC_DEBUG=D plus INPUT & OUTPUT HELPs tracingv KDC_DEBUG=A: KDC_DEBUG=M plus all format tracing


Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_LGSA_VERIFYDo not modify this parameter except under the guidance of IBM Software Support. This parameterinvokes the TMS:Engine to check that the $GSA address is available.



Parameter nameLGSA(&XI5LGSA)

Default valueY



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_LSRPOOL_BUFFER_NUMUse the KI5_X_AGT_LSRPOOL_BUFFER_NUM parameter to specify the number of virtual storagebuffers to be allocated for a buffer pool in the VSAM resource pool. You must specify both a buffer sizeand the number of buffers for each LSRPOOL statement; you cannot string the definitions. Use thissyntax to specify the buffer size and the number of buffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)



Parameter nameLSRPOOL(&XI5BSIZ, &XI5BNUM)

Default value32



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_LSRPOOL_BUFSIZEUse the KI5_X_AGT_LSRPOOL_BUFSIZE parameter to specify the size, in bytes, of each virtual storagebuffer in the buffer pool in the VSAM resource pool. You must specify a buffer size and number ofbuffers for each LSRPOOL statement; you cannot string the definitions. Use this syntax to specify thebuffer size and the number of buffers in the same parameter:LSRPOOL(buffer_size,number_of_buffers)



Parameter nameLSRPOOL(&XI5BSIZ, &XI5BNUM)

Default value32768



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_SDUMP_SVC_SYS1_DUMPDo not modify this parameter except under the guidance of IBM Software Support. This commandgenerates SVC dumps.



Parameter nameSDUMP(&XI5DSVC)

Default valueY

Permissible valuesY, N, S or Mv The Y parameter value directs the SVC dump to a system dump data set

(SYS1.DUMPxx). Before you specify the Y value, ensure that the TMS:Enginejob step isAPF-authorized and that the SYS1.DUMPxx data sets are large enough to contain thecontents of the TMS:Engine address space.

v The N parameter value directs formatted dumps to the RKLVSNAP data set. Ifpossible, avoid formatted dumps because these types of dumps disable the TMS:Engineaddress space for a longer time than either SVC dumps or SYSMDUMPs, and are moredifficult to analyze.

v The S parameter value directs summary dumps to the RKLVSNAP data set. Asummary dump consists of an ABEND summary and dispatcher summary and doesnot provide enough information for reliable problem analysis. Use this setting forspecific testing purposes only.

v The M parameter value directs ABEND dumps to the data set with the SYSMDUMPDD name. This type of dump is not formatted by the operating system and must beanalyzed with IPCS. Only the first dump taken is captured in the SYSMDUMP datasetunless JCL specifies DISP=MOD. The TMS:Engine automatically initializes theSYSMDUMP data set with an end-of-file mark.


Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_STORAGE_LIMIT_EXTENDUse the KI5_X_AGT_STORAGE_LIMIT_EXTEND parameter to specify the maximum size for theTMS:Engine extended storage (above-the-line) request.



Parameter nameLIMIT(&XI5ELIM, X)

Default value23


The maximum extended storage request size is specified as a power of 2. The minimumextended storage size is 16, which specifies a limit of 64K. The maximum is 25, whichspecifies a limit of 32M.


Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_STORAGE_LIMIT_PRIMARYUse the KI5_X_AGT_STORAGE_LIMIT_PRIMARY parameter to specify the maximum size for theTMS:Engine primary storage request.



Parameter nameLIMIT(&XI5PLIM, P)

Default value20


The maximum primary storage request size is specified as a power of 2. The minimumprimary storage size is 16, which specifies a limit of 64K. The maximum is 25, whichspecifies a limit of 32M.


Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY”v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_STORAGE_RESERVE_EXTUse the KI5_X_AGT_STORAGE_RESERVE_EXT parameter to specify the number of kilobytes (K) ofextended (above-the-line) storage to reserve for other routines that might perform their own GETMAINsin this address space. If your RESERVE value is too small, you might encounter IST566I messages fromVTAM or S80A, S878, S066, S40D, or S0F9 abends.



Parameter nameRESERVE(&XAGERES, X)

Default value4096



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_RESERVE_PRI” on page 152v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


KI5_X_AGT_STORAGE_RESERVE_PRIUse the KI5_X_AGT_STORAGE_RESERVE_PRI parameter to specify the number of kilobytes (K) ofprimary (below-the-line) storage to reserve for other routines (for example ACF2 and RACF) that mightperform their own GETMAINs in this address space. The ACF2 and RACF routines use approximately 1Kof primary storage per logged-on user. If your RESERVE value is too small, you might encounterISST566I messages from VTAM or S80A, S878, S066, S40D or S0F9 abends.



Parameter nameRESERVE(&XI5PRES, P)

Default value4096



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_KDC_DEBUG” on page 144v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_RESERVE_EXT” on page 151v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153v “KI5_X_AGT_TASKS_ATTACHED_NUM” on page 154


KI5_X_AGT_STORAGE_STGDEBUGUse the KI5_X_AGT_STORAGE_STGDEBUG parameter to activate TMS:Engine storage debuggingservices.



Parameter nameSTGDEBUG(&XI5STDB)

Default valueN

Permissible valuesY, N or Xv The Y value specifies to record basic storage debugging information.v The N parameter value specifies not to record basic storage debugging information.v The X value specifies to record extended storage debugging information.



Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150


KI5_X_AGT_TASKS_ATTACHED_NUMDo not modify this parameter except under the guidance of IBM Software Support. This parameterspecifies the number of general-purpose subtasks to be attached in the TMS:Engine address space. If theTMS:Engine is running on a multiprocessor, the TASKS default increases both the throughput and theCPU usage. Reducing the number of tasks decreases throughput and CPU usage.



Parameter nameTASKS(&XI5TASK)

Default value1

Permissible valuesDo not modify this parameter except under the guidance of IBM Software Support.


Related parametersv “KI5_X_AGT_CONFIRM_SHUTDOWN” on page 142v “KI5_X_AGT_DEBUG_TRACE” on page 143v “KI5_X_AGT_LGSA_VERIFY” on page 145v “KI5_X_AGT_LSRPOOL_BUFFER_NUM” on page 146v “KI5_X_AGT_LSRPOOL_BUFSIZE” on page 147v “KI5_X_AGT_SDUMP_SVC_SYS1_DUMP” on page 148v “KI5_X_AGT_STORAGE_LIMIT_EXTEND” on page 149v “KI5_X_AGT_STORAGE_LIMIT_PRIMARY” on page 150v “KI5_X_AGT_STORAGE_STGDEBUG” on page 153


Appendix A. Documentation library

This appendix contains information about the publications related to the OMEGAMON XE products andto IBM Tivoli Monitoring and the commonly shared components of Tivoli Enterprise Monitoring Server.These publications are listed in the following categories:v “OMEGAMON XE for IMS publications”v “Shared OMEGAMON XE publications” on page 156v “IBM Tivoli Monitoring library” on page 156v “Related publications” on page 158

See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide, SC23-8816, for informationabout accessing and using the publications. You can find the Documentation Guide in the IBM TivoliMonitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

To find a list of new and changed publications, click What's new on the Welcome page of the IBM TivoliMonitoring and OMEGAMON XE Information Center. To find publications from the previous version ofa product, click Previous information centers on the Welcome page for the product.

OMEGAMON XE for IMS publicationsThe following publications provide information about the OMEGAMON XE for IMS product:v Program Directory, GI13-2251

Contains information about the material and procedures that are associated with the installation ofOMEGAMON XE for IMS on z/OS. The Program Directory is intended for the system programmerwho is responsible for program installation and maintenance.

v Planning and Configuration Guide, SC27-4441

Documents the planning and configuration tasks necessary for the implementation of OMEGAMONXE for IMS on z/OS. This document is written for system administrators and others who areresponsible for installing and configuring OMEGAMON XE for IMS.

v User's Guide, SC27-4440

Introduces the features, workspaces, attributes, and predefined situations for the OMEGAMON XE forIMS product and supplements the user assistance provided with this product.

v Parameter Reference, SC27-4430

Provides reference information about the parameters that are used to set and store configuration valuesfor the runtime environments in which the OMEGAMON XE for IMS monitoring agent andtheOMEGAMON II for IMS components are configured.

v Troubleshooting Guide, SC27-4438

Provides explanations for the messages issued by the OMEGAMON XE for IMS product and theOMEGAMON II for IMS component.

v OMEGAMON for IMS User's Guide, SC27-4439

Describes in detail all of the features of the OMEGAMON XE for IMS (classic) interfacev Realtime Commands Reference, SC27-4437

Describes in detail all of the features of the OMEGAMON XE for IMS command interface.v Bottleneck Analysis Reference, SC27-4436

Provides reference information and descriptions of the features of the bottleneck analysis component.v Response Time Analysis Reference, SC27-4435


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/


Provides reference information and descriptions of the features of the response time analysis (RTA)component.

v Application Trace Facility Reference, SC27-4434

Explains how the Application Trace Facility (ATF) monitors and collects detailed information on IMSand Data base Control (DBCTL) transactions to help you analyze and improve performance.

v Historical Component (EPILOG) User's Guide, SC27-4433

Teaches you, step-by-step, how to operate the historical component (EPILOG) reporter after installation.v Historical Component (EPILOG) Reference, SC27-4432

Provides a comprehensive description of the features of the historical component (EPILOG).v Transaction Reporting Facility Reference, SC27-4431

Provides user and reference information about the features of the batch Transaction Reporting Facilitycomponents.

Shared OMEGAMON XE publicationsThe following publications provide information common to the OMEGAMON XE products:v Quick Start Guide, GI11-8918

Summarizes the installation and setup of an OMEGAMON XE monitoring agent on z/OS.v Common Planning and Configuration Guide, SC23-9734

Gives instructions for planning and configuration tasks common to the components of TivoliManagement Services on z/OS and the OMEGAMON XE monitoring agents on z/OS.

v Upgrade Guide, SC23-9745

Gives instructions for complete and staged upgrades of the OMEGAMON XE products.v End-to-End Response Time Feature Reference, SC27-2303

Provides instructions and reference information for the End-to-End Response Time Feature, whichsupplies response time data to several OMEGAMON XE products.

v Reports for Tivoli Common Reporting, SC27-2304

Explains how to use the Tivoli Common Reporting tool to create reports from data displayed in theTivoli Enterprise Portal and stored in the Tivoli Data Warehouse database.

v Common Parameter Reference, SC14-7280

Provides reference information about the parameters that are used to set up runtime environments andconfigure hub and remote Tivoli Enterprise Monitoring Servers on z/OS.

v PARMGEN Reference, SC22-5435

Provides detailed instructions and common configuration scenarios for creating and maintainingruntime environments by using the PARMGEN configuration method.

v Enhanced 3270 User Interface Guide, SC22-5426

Describes the features of the interface and provides operating instructions and reference material.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring V6.2 and about thecommonly shared components of Tivoli Enterprise Monitoring Server:v Quick Start Guide, GI11-8058

Introduces the components of IBM Tivoli Monitoring.v Exploring IBM Tivoli Monitoring, SC32-1803

Provides a series of exercises to help you explore IBM Tivoli Monitoring. By completing the activitiesin this workbook, you will install and configure your monitoring environment, explore both thegraphical and command-line interfaces of the product, use some of the new features, and work withseveral monitoring agents.


v Installation and Setup Guide, GC32-9407

Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows,Linux, and UNIX systems.

v Program Directory for IBM Tivoli Management Services on z/OS, GI11-4105

Gives instructions for the SMP/E installation of the Tivoli Enterprise Monitoring Server components onz/OS.

v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC27-2313

Gives detailed instructions for using the Configuration Tool to configure Tivoli Enterprise MonitoringServer on z/OS systems. Includes scenarios for using batch mode to replicate monitoring environmentsacross the z/OS enterprise. Also provides instructions for setting up security and for addingapplication support to a Tivoli Enterprise Monitoring Server on z/OS.

v Administrator's Guide, SC32-9408

Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v Tivoli Enterprise Portal online helpProvides context-sensitive reference information about all features and customization options of theTivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli EnterprisePortal.

v User's Guide, SC32-9409

Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons anddetailed instructions for all Tivoli Enterprise Portal features.

v Command Reference, SC32-6045

Provides detailed syntax and parameter information and examples of the commands you can use inIBM Tivoli Monitoring.

v Troubleshooting Guide, GC32-9458

Provides information to help you troubleshoot problems with the software.v Deployment Guide, SC23-8873

Outlines key activities such as planning, maintenance, and tuning considerations that are needed toensure a successful deployment of your IBM Tivoli Monitoring environment.

v Messages, SC23-7969

Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Enterprise Monitoring Server components (such as Tivoli Enterprise Monitoring Server on z/OSand TMS:Engine).

v Upgrading from V5.1.2, GC32-1976

Gives instructions for upgrading custom resource models from IBM Tivoli Monitoring V5.1.2 to IBMTivoli Monitoring V6.2.

v IBM Tivoli Universal Agent User's Guide, SC32-9459

Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM TivoliUniversal Agent enables you to use the monitoring and automation capabilities of IBM TivoliMonitoring to monitor any type of data you collect.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461

Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and providesdescriptions, syntax, and return status codes for the API calls and command-line interface commands.

v Agent Builder User's Guide, SC32-1921

Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

v Fix Pack Readme and Documentation Addendum

Describes the installation process for a fix pack and provides updated information on problems andworkarounds associated with the fix pack. A new version of this document is created for each fix pack.

Appendix A. Documentation library 157

Related publicationsYou can find useful information about the OMEGAMON XE Tivoli Enterprise Monitoring Agents in theIBM Tivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.




Appendix B. Accessibility

Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, touse software products successfully. OMEGAMON XE monitoring products support several userinterfaces. Product functionality and accessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what

is displayed on the screen. Consult the product documentation of the assistive technology for detailson using those technologies with this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to give the maximum

opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users with vision

impairments can understand the contents of the images.

The OMEGAMON XE on z/OS Information Center, and its related publications, are accessibility-enabled.The accessibility features of the information center are described at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html.

Interface information

The Tivoli Enterprise Portal interface offers the greatest range of functionality, but is not entirelyaccessible. The OMEGAMON enhanced 3270 user interface offers more limited functionality, but isentirely accessible. (The enhanced 3270 user interface supports all the accessibility features supported byyour emulator. If you are using IBM Personal Communications, you can find information on itsaccessibility features at http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm. If you are using a third-party emulator, seethe documentation for that product for accessibility information.)

The OMEGAMON ("classic") and OMEGAMON II (CUA) 3270 interfaces use an ISPF style interface.Standard and custom PF Key settings, menu options, and command-line interface options allow for shortcuts to commonly viewed screens. While basic customization options allow for highlights and othereye-catcher techniques to be added to the interface, the customization options are limited.

Related accessibility information

You can view the publications for OMEGAMON XE for IMS on z/OS in Adobe Portable DocumentFormat (PDF) using the Adobe Acrobat Reader. The PDFs are provided on a CD that is packaged withthe product, or you can access them at http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment thatIBM has to accessibility.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm

http://www.ibm.com/able


Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides thefollowing ways for you to obtain support:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.htmland follow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the IBM Tivoli OMEGAMON XE for IMS onz/OS: Troubleshooting Guide.


http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa


Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conformingto IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. ©Copyright IBM Corp. _enter the year or years_. All rights reserved.


TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web atCopyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Notices 165


Index

Aaccessibility features 159

Bbatch mode

parameters 4using 4

Batch parameter name 2BMP application group information

KI2_CLASSIC_RACF_BMP_APPL_GRP 62KI2_CLASSIC_RACF_BMP_APPL_GWK 63

Cconfiguration parameters 1

groupings 7, 97OMEGAMON II for IMS 7OMEGAMON XE for IMS on z/OS 97overview 1

configuration profile 2, 3generating and editing 3parameter groupings 7, 97

Configuration Toolparameters 4using 4

Configuration Tool field name 2

Ddefault values 4documentation 155

EError recovery information

KI2_PSM_ERP_COUNT 65

HHigh-level qualifier for z/OS automation interface exit agent

KI2_CUA_OMEGCTR_HILEV 64

IIBM Support Assistant 161IMS and IRLM subsystem information

KI5_II 99KI5_IInn_ROW 100KI5_IInn_SS_AUTO 102KI5_IInn_SS_CONFLICT 103KI5_IInn_SS_COUPFAC 104KI5_IInn_SS_DBCMSK 105KI5_IInn_SS_DBCTHR 106KI5_IInn_SS_DEX 107KI5_IInn_SS_DSHR 108KI5_IInn_SS_ENV 109KI5_IInn_SS_HADB 110

IMS and IRLM subsystem information (continued)KI5_IInn_SS_HLTH 111KI5_IInn_SS_ICMD 130KI5_IInn_SS_LCK 112KI5_IInn_SS_MQSTAT 113KI5_IInn_SS_MSC 114KI5_IInn_SS_OSAM 115KI5_IInn_SS_OTMA 116KI5_IInn_SS_PARM 117KI5_IInn_SS_POOLS 118KI5_IInn_SS_RESOURCE 119KI5_IInn_SS_RGO 120KI5_IInn_SS_RTAETE 121KI5_IInn_SS_RTAEXCP 122KI5_IInn_SS_RTAGRPH 123KI5_IInn_SS_RTAINTV 124KI5_IInn_SS_RTARMON 125KI5_IInn_SS_RTASLOT 126KI5_IInn_SS_SHRQ 127KI5_IInn_SS_TYP 128KI5_IInn_SS_WORK 129KI5_IInn_SSID 101

IMS Connect settingsKI5_COMP 131KI5_COMPnn_ICON_NAME 132KI5_COMPnn_ROW 133KI5_COMPnn_TYPE 134KI5_ICT_AUTODISCOVER 135KI5_ICT_BUFFER_SIZE 136KI5_ICT_BUFFER_THRESH 137KI5_ICT_COLLECT_INTERVAL 138KI5_ICT_COLLECT_LEVEL 139KI5_ICT_MESSAGE_LEVEL 140KI5_X_ICT_IMS_CONNECT_FLAG 141

ISA 161

KKI2_CLASSIC_ATF_ATFBUFF parameter 42KI2_CLASSIC_ATF_AUTORESTART parameter 43KI2_CLASSIC_ATF_BUFFSIZE parameter 44KI2_CLASSIC_ATF_SANDBOX parameter 45KI2_CLASSIC_ATF_STOR parameter 46KI2_CLASSIC_ATF_TRACE parameter 47KI2_CLASSIC_ATFI2 parameter 41KI2_CLASSIC_ATTCH_CMD_BMP parameter 37KI2_CLASSIC_DED_SESS parameter 38KI2_CLASSIC_DEXAN parameter 48KI2_CLASSIC_EPILOG parameter 49KI2_CLASSIC_RACF_BMP_APPL_GRP parameter 62KI2_CLASSIC_RACF_BMP_APPL_GWK parameter 63KI2_CLASSIC_RTA parameter 50KI2_CLASSIC_RTA_SLOUGH parameter 51KI2_CLASSIC_RTA_XCFGROUP parameter 52KI2_CLASSIC_SAP_SUPPORT parameter 39KI2_CLASSIC_STC_NUM parameter 24KI2_CLASSIC_STC_PREFIX parameter 10KI2_CLASSIC_TRF parameter 53KI2_CLASSIC_TRF_BMP parameter 54KI2_CLASSIC_TRF_DB2 parameter 56KI2_CLASSIC_TRF_DBD parameter 55


KI2_CLASSIC_TRF_DL1 parameter 57KI2_CLASSIC_TRF_FP parameter 58KI2_CLASSIC_TRF_LOG parameter 59KI2_CLASSIC_TRF_LOGREC_ID parameter 60KI2_CLASSIC_UMAX parameter 11KI2_CLASSIC_VSAM_MSG_LOG parameter 61KI2_CLASSIC_VTAM_APPL_PREFIX parameter 12KI2_CLASSIC_VTAM_CONNECT parameter 40KI2_CLASSIC_VTAM_NODE_PREFIX parameter 13KI2_CUA_OMEGCTR_HILEV 64KI2_CUA_STC parameter 14KI2_CUA_VTAM_APPL_CMD parameter 15KI2_CUA_VTAM_APPL_I/CF parameter 16KI2_CUA_VTAM_APPL_LOGON parameter 17KI2_CUA_VTAM_APPL_OPERATOR parameter 18KI2_CUA_VTAM_APPL_PREFIX parameter 19KI2_CUA_VTAM_NODE parameter 20KI2_CUA_VTAM_VTPOOL_NUM parameter 21KI2_CUA_VTAM_VTPOOL_PREFIX parameter 22KI2_CUA_WTO_MSG parameter 23KI2_I1 parameter 25KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR 26KI2_I1nn_CLASSIC_IMS_RESLIB parameter 28KI2_I1nn_CLASSIC_IMSID parameter 27KI2_I1nn_CLASSIC_LROWS 29KI2_I1nn_CLASSIC_MPREFIX parameter 30KI2_I1nn_CLASSIC_STC parameter 31KI2_I1nn_CLASSIC_USER_PROFILE 32KI2_I1nn_CLASSIC_VTAM_APPL_LOGON 33KI2_I1nn_CLASSIC_VTAM_NODE parameter 34KI2_I1nn_CLASSIC_XMIT parameter 35KI2_I1nn_ROW parameter 36KI2_MIG_HILEV 66KI2_MIG_OLD_EPILOG_$DEF 69KI2_MIG_OLD_EPILOG_@DEF 70KI2_MIG_OLD_EPILOG_DSTOR 67KI2_MIG_OLD_EPILOG_OPT 68KI2_MIG_OLD_NAM 71KI2_MIG_OLD_PROF 72KI2_MIG_OLD_SCRN_SPC 73KI2_MIG_OLD_TDB 74KI2_MIG_VER 75KI2_PSM_ERP_COUNT 65KI2_X_IMS_CONFIRM_SHUTDOWN 76KI2_X_IMS_DEBUG_TRACE 77KI2_X_IMS_LGSA_VERIFY 78KI2_X_IMS_LOGBLOCK_SIZE 79KI2_X_IMS_LSRPOOL_BUFFER_NUM1 80KI2_X_IMS_LSRPOOL_BUFFER_NUM2 81KI2_X_IMS_LSRPOOL_BUFFER_NUM3 82KI2_X_IMS_LSRPOOL_BUFSIZE1 83KI2_X_IMS_LSRPOOL_BUFSIZE2 84KI2_X_IMS_LSRPOOL_BUFSIZE3 85KI2_X_IMS_SDUMP_SVC_SYS1_DUMP 86KI2_X_IMS_STORAGE_LIMIT_EXTEND 87KI2_X_IMS_STORAGE_LIMIT_PRIMARY 88KI2_X_IMS_STORAGE_MIN_EXTEND 89KI2_X_IMS_STORAGE_MIN_PRIMARY 90KI2_X_IMS_STORAGE_RESERVE_EXT 91KI2_X_IMS_STORAGE_RESERVE_PRI 92KI2_X_IMS_STORAGE_STGDEBUG 93KI2_X_SECURITY_RESOURCE_CLASS 94KI2_X_SECURITY_USER_EXIT 95KI2_X_STC_INCLUDE_IMSMON_FLAG 96KI2SYSIN 1KI5_COMP 131KI5_COMPnn_ICON_NAME 132

KI5_COMPnn_ROW 133KI5_COMPnn_TYPE 134KI5_ICT_AUTODISCOVER 135KI5_ICT_BUFFER_SIZE 136KI5_ICT_BUFFER_THRESH 137KI5_ICT_COLLECT_INTERVAL 138KI5_ICT_COLLECT_LEVEL 139KI5_ICT_MESSAGE_LEVEL 140KI5_II 99KI5_IInn_ROW 100KI5_IInn_SS_AUTO 102KI5_IInn_SS_CONFLICT 103KI5_IInn_SS_COUPFAC 104KI5_IInn_SS_DBCMSK 105KI5_IInn_SS_DBCTHR 106KI5_IInn_SS_DEX 107KI5_IInn_SS_DSHR 108KI5_IInn_SS_ENV 109KI5_IInn_SS_HADB 110KI5_IInn_SS_HLTH 111KI5_IInn_SS_ICMD 130KI5_IInn_SS_LCK 112KI5_IInn_SS_MQSTAT 113KI5_IInn_SS_MSC 114KI5_IInn_SS_OSAM 115KI5_IInn_SS_OTMA 116KI5_IInn_SS_PARM 117KI5_IInn_SS_POOLS 118KI5_IInn_SS_RESOURCE 119KI5_IInn_SS_RGO 120KI5_IInn_SS_RTAETE 121KI5_IInn_SS_RTAEXCP 122KI5_IInn_SS_RTAGRPH 123KI5_IInn_SS_RTAINTV 124KI5_IInn_SS_RTARMON 125KI5_IInn_SS_RTASLOT 126KI5_IInn_SS_SHRQ 127KI5_IInn_SS_TYP 128KI5_IInn_SS_WORK 129KI5_IInn_SSID 101KI5_X_AGT_CONFIRM_SHUTDOWN 142KI5_X_AGT_DEBUG_TRACE 143KI5_X_AGT_KDC_DEBUG 144KI5_X_AGT_LGSA_VERIFY 145KI5_X_AGT_LSRPOOL_BUFFER_NUM 146KI5_X_AGT_SDUMP_SVC_SYS1_DUMP 148KI5_X_AGT_STORAGE_LIMIT_EXTEND 149KI5_X_AGT_STORAGE_LIMIT_PRIMARY 150KI5_X_AGT_STORAGE_RESERVE_PRI 151, 152KI5_X_AGT_STORAGE_STGDEBUG 153KI5_X_AGT_TASKS_ATTACHED_NUM 147, 154KI5_X_ICT_IMS_CONNECT_FLAG 141KI5ENV 1KI5SYSIN 1

Llibraries

IBM Tivoli Monitoring 156OMEGAMON XE shared publications 156

location of stored parameters 1

MMigration options

KI2_MIG_HILEV 66


Migration options (continued)KI2_MIG_OLD_EPILOG_$DEF 69KI2_MIG_OLD_EPILOG_@DEF 70KI2_MIG_OLD_EPILOG_DSTOR 67KI2_MIG_OLD_EPILOG_OPT 68KI2_MIG_OLD_NAM 71KI2_MIG_OLD_PROF 72KI2_MIG_OLD_SCRN_SPC 73KI2_MIG_OLD_TDB 74KI2_MIG_VER 75

OOMEGAMON for IMS 3270 connection options

KI2_CLASSIC_ATTCH_CMD_BMP 37KI2_CLASSIC_DED_SESS 38KI2_CLASSIC_SAP_SUPPORT 39KI2_CLASSIC_VTAM_CONNECT 40

OMEGAMON for IMS 3270 data collection optionsApplication Trace Facility (ATF)

KI2_CLASSIC_ATF_ATFBUFF 42KI2_CLASSIC_ATF_AUTORESTART 43KI2_CLASSIC_ATF_BUFFSIZE 44KI2_CLASSIC_ATF_SANDBOX 45KI2_CLASSIC_ATF_STOR 46KI2_CLASSIC_ATF_TRACE 47KI2_CLASSIC_ATFI2 41

KI2_CLASSIC_DEXAN 48KI2_CLASSIC_EPILOG 49KI2_CLASSIC_RTA 50KI2_CLASSIC_RTA_SLOUGH 51KI2_CLASSIC_RTA_XCFGROUP 52KI2_CLASSIC_VSAM_MSG_LOG 61Transaction Reporting Facility (TRF)

KI2_CLASSIC_TRF 53KI2_CLASSIC_TRF_BMP 54KI2_CLASSIC_TRF_DB2 56KI2_CLASSIC_TRF_DBD 55KI2_CLASSIC_TRF_DL1 57KI2_CLASSIC_TRF_FP 58KI2_CLASSIC_TRF_LOG 59KI2_CLASSIC_TRF_LOGREC_ID 60

OMEGAMON II (CUA) monitoring agentKI2_CLASSIC_UMAX 11KI2_CLASSIC_VTAM_APPL_PREFIX 12KI2_CLASSIC_VTAM_NODE_PREFIX 13KI2_CUA_STC 14KI2_CUA_WTO_MSG 23Realtime Monitor

KI2_I1nn_CLASSIC_CTRL_UNIT_ADDR 26KI2_I1nn_CLASSIC_IMS_RESLIB 28KI2_I1nn_CLASSIC_IMSID 27KI2_I1nn_CLASSIC_LROWS 29KI2_I1nn_CLASSIC_MPREFIX 30KI2_I1nn_CLASSIC_STC 31KI2_I1nn_CLASSIC_USER_PROFILE 32KI2_I1nn_CLASSIC_VTAM_APPL_LOGON 33KI2_I1nn_CLASSIC_VTAM_NODE 34KI2_I1nn_CLASSIC_XMIT 35KI2_I1nn_ROW 36

VTAMKI2_CUA_VTAM_APPL_CMD 15KI2_CUA_VTAM_APPL_I/CF 16KI2_CUA_VTAM_APPL_LOGON 17KI2_CUA_VTAM_APPL_OPERATOR 18KI2_CUA_VTAM_APPL_PREFIX 19KI2_CUA_VTAM_NODE 20

OMEGAMON II (CUA) monitoring agent (continued)VTAM (continued)

KI2_CUA_VTAM_VTPOOL_NUM 21KI2_CUA_VTAM_VTPOOL_PREFIX 22

OMEGAMON II for IMSconfiguration parameters 7

OMEGAMON II for IMS settingsKI2_X_IMS_CONFIRM_SHUTDOWN 76KI2_X_IMS_DEBUG_TRACE 77KI2_X_IMS_LGSA_VERIFY 78KI2_X_IMS_LOGBLOCK_SIZE 79KI2_X_IMS_LSRPOOL_BUFFER_NUM1 80KI2_X_IMS_LSRPOOL_BUFFER_NUM2 81KI2_X_IMS_LSRPOOL_BUFFER_NUM3 82KI2_X_IMS_LSRPOOL_BUFSIZE1 83KI2_X_IMS_LSRPOOL_BUFSIZE2 84KI2_X_IMS_LSRPOOL_BUFSIZE3 85KI2_X_IMS_SDUMP_SVC_SYS1_DUMP 86KI2_X_IMS_STORAGE_LIMIT_EXTEND 87KI2_X_IMS_STORAGE_LIMIT_PRIMARY 88KI2_X_IMS_STORAGE_MIN_EXTEND 89KI2_X_IMS_STORAGE_MIN_PRIMARY 90KI2_X_IMS_STORAGE_RESERVE_EXT 91KI2_X_IMS_STORAGE_RESERVE_PRI 92KI2_X_IMS_STORAGE_STGDEBUG 93KI2_X_SECURITY_RESOURCE_CLASS 94KI2_X_SECURITY_USER_EXIT 95KI2_X_STC_INCLUDE_IMSMON_FLAG 96

OMEGAMON II monitoring agentKI2_CLASSIC_SAP_SUPPORT 24KI2_CLASSIC_STC_PREFIX 10Realtime Monitor tasks 24

OMEGAMON XE for IMS monitoring agentKI5_X_AGT_CONFIRM_SHUTDOWN 142KI5_X_AGT_DEBUG_TRACE 143KI5_X_AGT_KDC_DEBUG 144KI5_X_AGT_LGSA_VERIFY 145KI5_X_AGT_LSRPOOL_BUFFER_NUM 146KI5_X_AGT_LSRPOOL_BUFSIZE 147KI5_X_AGT_SDUMP_SVC_SYS1_DUMP 148KI5_X_AGT_STORAGE_LIMIT_EXTEND 149KI5_X_AGT_STORAGE_LIMIT_PRIMARY 150KI5_X_AGT_STORAGE_RESERVE_EXT 151KI5_X_AGT_STORAGE_RESERVE_PRI 152KI5_X_AGT_STORAGE_STGDEBUG 153KI5_X_AGT_TASKS_ATTACHED_NUM 154

OMEGAMON XE for IMS on z/OSconfiguration parameters 97

overriding default values 4

Pparameter name 2

Batch parameter name 2Configuration Tool field name 2

parameters 1, 2configuration 1default values 4location where stored 1

PARMGEN configuration methodconfiguration profile 2defined 2groupings of parameters 2parameters used by 2

publicationsIBM Tivoli Monitoring 156OMEGAMON XE 156

Index 169

publications (continued)related 158shared 156Tivoli Management Services on z/OS 156types 155

RRealtime Monitor

KI2_I1 25OMEGAMON II (CUA) monitoring agent 25

Sshared publications 156Software Support 161support assistant 161


Readers’ Comments — We'd Like to Hear from You

IBM Tivoli OMEGAMON XE for IMS on z/OSParameter ReferenceVersion 5.1.0

Publication No. SC27-4430-00

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Send your comments to the address on the reverse side of this form.

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouSC27-4430-00

SC27-4430-00

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Printed in USA

SC27-4430-00

Date post:	07-May-2018
Category:	Documents
Upload:	vuhuong
View:	233 times
Download:	1 times