end-to-end responsetime feature reference...executable code has been separated from the...

OMEGAMON and IBM Tivoli Management Services on z/OSVersion 6.2.0

End-to-End Response Time FeatureReference

SC27-2303-02

��

Notices

This edition applies to version 6, release 2, modification 0 of IBM Tivoli End-to-End Response Time Feature(product number HKET620 and to all subsequent releases and modifications until otherwise indicated in neweditions. This edition replaces SC32-9376-01 and SC27-2303-00.

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

Contents

Figures . . . . . . . . . . . . . . . v

About this information . . . . . . . . vii

Chapter 1. Introduction . . . . . . . . 1New in this release . . . . . . . . . . . . 1Hardware and software requirements . . . . . . 2Installing and configuring ETE . . . . . . . . 3

Chapter 2. Understanding end-to-endresponse time . . . . . . . . . . . . 5How ETE calculates response time . . . . . . . 5

Chapter 3. Starting ETE . . . . . . . . 7Stopping ETE. . . . . . . . . . . . . . 10Recycling a major node . . . . . . . . . . 10Recycling ETE . . . . . . . . . . . . . 10Customizing for a multi-session manager product 10Determining which products are using ETE services 11

Chapter 4. Running multiple copies ofETE . . . . . . . . . . . . . . . . 13

Chapter 5. Customizing ETE to workwith a multi-session manager . . . . . 15

Chapter 6. Customizing ETE to workwith a multi-session manager . . . . . 19

Chapter 7. ETE commands . . . . . . 23ETE command syntax . . . . . . . . . . . 23ETE CLRDUMP . . . . . . . . . . . . . 23ETE DUMP . . . . . . . . . . . . . . 23ETE DUMPDXL . . . . . . . . . . . . . 24ETE HELP. . . . . . . . . . . . . . . 24ETE NOVERBOSE . . . . . . . . . . . . 24ETE QUIESCE . . . . . . . . . . . . . 25ETE RESET . . . . . . . . . . . . . . 25ETE SYSTEMS . . . . . . . . . . . . . 26ETE TRACEOFF . . . . . . . . . . . . . 26ETE TRACEON . . . . . . . . . . . . . 26ETE USER=userid . . . . . . . . . . . . 26ETE USERS . . . . . . . . . . . . . . 27

Chapter 8. Creating a device exclusionlist . . . . . . . . . . . . . . . . 29

Chapter 9. Using the CICS definiteresponse . . . . . . . . . . . . . . 31CICS definite response solution provided . . . . 31CICS definite response graphic overview . . . . 31CICS releases supported . . . . . . . . . . 32

Multi-session manager considerations . . . . . 32Installation considerations . . . . . . . . . 32CICS table updates required . . . . . . . . . 33ETE EXEC Parameter CIHT . . . . . . . . . 33CICS SEND exit . . . . . . . . . . . . . 34

Enabling and disabling the exit using PLTPI orPLTSD . . . . . . . . . . . . . . . 34Enabling and disabling the exit using transactionKETX . . . . . . . . . . . . . . . 34

Chapter 10. Reporting ETE problems 35Procedure for reporting a problem. . . . . . . 35

Chapter 11. ETE troubleshooting . . . 37ABEND 0C4 received with the ETE started task . . 37ABEND 0D6 when running with any OMEGAMONagent using ETE services . . . . . . . . . . 38Definite response unit failures in VTAM, DB2, andCICS . . . . . . . . . . . . . . . . 38ETE address space abends with error code U0404 . 39ETE message ETE0101: ETE COULD NOT BESTARTED. VTAM NOT INITIALIZED OR VTAM ISAT AN UNSUPPORTED LEVEL logged . . . . . 39ETE storage usage is excessive . . . . . . . . 39Multiple load attempts per day of ETE modulesmade trying to initialize the ETE subsystem . . . 40OMEGAMON II for IMS Message OEI971EPILOG/IMS ETE INSTALL FAILED ETE IS NOTACTIVE logged . . . . . . . . . . . . . 41OMEGAMON II for MVS message OM8389: RTANot Operational. RC=20 RSC=8000001E; RTA: TSOlight is blue, meaning inactive . . . . . . . . 41OMEGAMON II for MVS message OM8389 RC=20SC=4080012A User Already Defined logged whenETE is restarted . . . . . . . . . . . . . 42SMP/E message GIM35908I logged when installingOMEGAMON II for CICS and OMEGAMON XE forCICS . . . . . . . . . . . . . . . . 42Startup request failed with message ETE0090 logged 42Users signing on to TSO through a multi-sessionmanager product are listed using the TSO HOSTcommand but not the ETE USERS command . . . 43

Documentation library . . . . . . . . 45IBM Tivoli OMEGAMON XE for MainframeNetworks publications. . . . . . . . . . . 45IBM Tivoli Monitoring library . . . . . . . . 46Documentation for the base agents . . . . . . 47Related publications . . . . . . . . . . . 47Other sources of documentation . . . . . . . 47

Support information . . . . . . . . . 49Using IBM Support Assistant . . . . . . . . 49Obtaining fixes . . . . . . . . . . . . . 50Receiving weekly support updates . . . . . . 50

© Copyright IBM Corp. 2008, 2011 iii

Contacting IBM Software Support . . . . . . . 50

Notices . . . . . . . . . . . . . . 53

Trademarks . . . . . . . . . . . . . . 54

Index . . . . . . . . . . . . . . . 55

iv OMEGAMON and IBM Tivoli Management Services on z/OS: End-to-End Response Time Feature Reference

Figures

1. Calculating response time . . . . . . . . 62. ETE USERS command output . . . . . . . 93. MSM configuration: real terminal using a

single VLU. . . . . . . . . . . . . 154. MSM configuration: real terminal using a

multiple VLUs . . . . . . . . . . . 165. MSM configuration: multiple real terminals

using a single VLU . . . . . . . . . . 16

6. MSM configuration: real terminal using asingle VLU. . . . . . . . . . . . . 19

7. MSM configuration: real terminal using amultiple VLUs . . . . . . . . . . . 20

8. MSM configuration: multiple real terminalsusing a single VLU . . . . . . . . . . 20

9. ETE DR Implementation for CICS . . . . . 32

© Copyright IBM Corp. 2008, 2011 v

vi OMEGAMON and IBM Tivoli Management Services on z/OS: End-to-End Response Time Feature Reference

About this information

IBM Tivoli OMEGAMON and IBM Tivoli Management Services on z/OS: End-to-End Response Time FeatureReference Version 6 Release 2 Modification Level 0 (Version 6.2.0) documents the End to End ResponseTime feature, a common component used by four OMEGAMON XE monitoring agents on z/OS: CICS,z/OS, IMS, and Mainframe Networks.

This information is for the z/OS systems programmer or analyst who is responsible for installingapplications, automating tasks on the system, monitoring new applications, and providing solutions foroperators when they have problems. This information is also useful for the program analyst who isresponsible for fine tuning the performance of systems (by measuring system capabilities and tweakingconfiguration settings).

Users of this information should be familiar with the z/OS operating system and its associated concepts,UNIX System Services, TCP/IP, and performance monitoring concepts.

This edition applies to version 6, release 2, modification 0 of IBM Tivoli End-to-End Response TimeFeature (product number HKET620 and to all subsequent releases and modifications until otherwiseindicated in new editions. This edition replaces SC32-9376-01 and SC27-2303-00.

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

© Copyright IBM Corp. 2008, 2011 vii

viii OMEGAMON and IBM Tivoli Management Services on z/OS: End-to-End Response Time Feature Reference

Chapter 1. Introduction

The IBM® Tivoli® End-to-End (ETE) Response Time Feature component captures end-to-end response timefor applications that use either the definite response protocol or the response time exception responseprotocol, timing SNA traffic that flows through VTAM®. This information was written for systemprogrammers and system analysts.

This guide provides the following information:v A description of ETEv An explanation of how to start ETE after installation and customization have been completedv A description of each ETE command argument.

The ETE procedure is installed into your procedure library during Configuration Tool configuration. Theconfiguration guide for each OMEGAMON® monitoring agent on z/OS® that incorporates ETE describesthe configuration process. For information on using ETE to monitor response time within a particularOMEGAMON agent, refer to the appropriate OMEGAMON agent documentation.

This guide is for the z/OS Systems Programmer/Analyst who is responsible for the following tasks:v Installing applications, such as the ETE productv Automating tasks on the systemv Monitoring new applicationsv Troubleshooting and providing solutions for operators when they have problems

This guide is also useful for the programmer analyst who is responsible for fine-tuning the performanceof systems (by measuring system capabilities and tweaking configuration settings). Readers should befamiliar with the following topics:v The z/OS operating system and its associated conceptsv UNIX System Servicesv TCP/IP and VTAMv Performance monitoring concepts

This section describes the End-to-End Response Time Feature (ETE), how it calculates response time,what is new in Version 6.2.0, and what hardware and software are supported.

New in this releaseThe following changes have been made in ETE for this version.v ETE has been reversioned from 560 to 6.2.0.v ETE has a new component FMID, HKET620.v Updates since the .00 version of this book to do the following:

– Clarify usage issues with the new NFNDFC=NO parameter in Chapter 3– A new topic in Chapter 3,“ Determining which products are using ETE services”– Updates to the troubleshooting chapter to document ABENDSA03

v ETE Version 6.2.0 is now configured using Configuration Tool version 3.1.0 or later. Updates to theConfiguration Tool have introduced the following changes in the ETE installation procedures.– Common configuration requirement for DFHRPL usage library and concatenation.– Redesign of base runtime environments and the runtime environment load function.

© Copyright IBM Corp. 2008, 2011 1

Executable code has been separated from the configuration data by the creation of a set of userlibraries. This separation eliminates the need to reconfigure each product after applying maintenancethrough SMP/E, and allows runtime environments sharing a base runtime environment to havemore control over their customized settings, such as security modules. A full or sharing runtimeenvironment now includes one or more of the following new user libraries, as required by theinstalled products:- RKANCMDU- RKANMODU- RKANPARU- RKANSAMU- RKANSQLU

The Configuration Tool provides a utility to allocate the new user libraries during upgrade. Theruntime environment load process copies the target libraries to their user counterparts in runtimelibraries in a base or a full runtime environment. If the runtime environment is set up to share theSMP/E target libraries directly, the load step is not required after applying SMP/E maintenance(unless the maintenance HOLDDATA information indicates otherwise). The redesign of the runtimeenvironment and the load function is available in a special programming enhancement (SPE).

v ETE now allocates the SSCVT control block using Key 0 CSA storage. Previously, this control block wasallocated using key 8. This fix addressed a security concern.

v ETE requires a PTF for each new version of z/OS where you install the product. Ensure that you haveapplied the PDF that corresponds to your z/OS versions

v Support for CICS® Transaction Server for z/OS Version 3.3, or later.

Hardware and software requirementsCertain terminal types are supported, as well as specified versions of z/OS Communications Server andthe OMEGAMON monitoring agents. ETE can coexist with previous versions and run on a single system.

Terminal types supported

ETE Version 6.2.0 provides response time data for the following real LU types:v SNA LU type 1v SNA LU type 2v SNA LU type 3

z/OS Communication Server releases supported

ETE Version 6.2.0 supports z/OS version 1.8 (VTAM version 618), or higher.

OMEGAMON XE monitoring agents on z/OS supported

ETE is an SNA response time monitor which runs as a subsystem. It provides a service to OMEGAMONXE monitoring agents on z/OS. ETE measures the host and network components of response time andfurnishes them to any OMEGAMON that displays response time. Currently, the OMEGAMON productsthat obtain response time from ETE and their minimum supported levels are as follows:v OMEGAMON XE for CICS, Version 3.1.0, or laterv OMEGAMON XE for IMS™, Version 3.1.0, or laterv OMEGAMON XE for Mainframe Networks, Version 3.1.0, or laterv OMEGAMON XE on z/OS, Version 3.1.0, or later

2 OMEGAMON and IBM Tivoli Management Services on z/OS: End-to-End Response Time Feature Reference

Running ETE on a single system

For all of the IBM Tivoli OMEGAMON products that use ETE Version 6.2.0 for response time, only oneETE Version 6.2.0 system is required, regardless of the number of IBM Tivoli OMEGAMON products youare running.

Coexistence with previous versions

ETE Version 6.2.0 running in one address space can coexist with a previous version of ETE running inanother address space.

You can run multiple ETE subsystems for testing, but for production, use the minimum number of ETEsystems required. For more information about running multiple ETE systems, see Chapter 4, “Runningmultiple copies of ETE,” on page 13.

Installing and configuring ETEETE is installed into your proclib when you configure the monitoring agent. Multiple OMEGAMONmonitoring agents can share the same ETE started task.

For each OMEGAMON XE monitoring agent on z/OS that you want to use the ETE product, the ETEproc is installed into your proclib when you configure the product using the Configuration Tool. YourOMEGAMON monitoring agents should share the same ETE started task.

For information about using the Configuration Tool, see the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide or the Configuration Tool onlinehelp.

The sections that follow explain how to further configure ETE for your site.

Chapter 1. Introduction 3

Chapter 2. Understanding end-to-end response time

ETE measures end-to-end response time for applications that use either definite response protocol orexception response protocol.

End-to-end response time is the elapsed time between the moment that a user presses a key (Enter, F1through F24, PA1, PA2, PA3, or Clear) and the moment that a response is received at the terminal. Forexample, if you start a stopwatch when a user presses Enter and stop it when the terminal receives theapplication's first response to the user's request, the stopwatch shows the end-to-end response time forthat request.

To measure end-to-end response time, ETE places itself inside one of the VTAM SNA layers. In thislocation ETE can time all SNA traffic that flows through VTAM. End-to-end response time measurementrequires that VTAM internal trace with the PIU option is active. The measurement is startedautomatically when ETE is activated.

ETE captures end-to-end response time for applications that use either the definite response protocol or theresponse time exception response protocol.v Definite response protocol: Under the definite response protocol, the application asks the terminal

controller to respond to transmitted data by indicating whether or not the transmission was successful.The application must then wait for the controller's response before continuing. Because the controllerresponds to all transmissions, end-to-end response time is relatively easy to monitor under the definiteresponse protocol.

v Exception response protocol: Under the exception response protocol, the application asks the controllerto respond only if an error occurs during data transmission to the terminal. Because ETE can measureend-to-end response time only for transactions that require a response from the controller, ETE mustturn on definite response for applications that use the exception response protocol. After it measuresthe response time, ETE discards the definite response before it flows to the application. As a result, theapplication never receives the definite response and is not even aware that a definite response waselicited

How ETE calculates response timeETE calculates response time by measuring the time between SNA events inside VTAM.

The measured time begins when the request flows through VTAM toward the application; it ends whenVTAM receives the definite response from the terminal controller. There is only one portion of end-to-endresponse time that ETE cannot capture directly and must estimate–the time before the user's requestreaches VTAM (T1 minus T0), as shown in Figure 1 on page 6:


In most cases, the time it takes a request to flow from the terminal to VTAM (T1 minus T0)approximately equals the amount of time it takes the definite response to flow from the controller toVTAM (T6 minus T5). This time calculation is true because all definite responses and most inboundrequests contain little data. Therefore, ETE calculates end-to-end response time as (T6 minus T1).

Figure 1. Calculating response time


Chapter 3. Starting ETE

Follow this process to start and verify ETE.

About this task

Attention: Do not start ETE until you have installed the component and customized it, as described inyour OMEGAMON monitoring agent configuration guides.

This chapter explains how to start ETE.

For information on using ETE within your OMEGAMON monitoring agent, refer to the ETE informationin your OMEGAMON monitoring agent on z/OS configuration guides.

To start ETE, use the following steps in sequential order.

Procedure1. Shut down all OMEGAMON components that use ETE. To shut down OMEGAMON components that

use ETE, complete the following steps.a. Stop all started tasks that use ETE. To determine what tasks are running that use ETE, issue the

ETE USERS command. See “ETE USERS” on page 27 for more information about this command. Forinformation about stopping and starting specific started tasks, refer to the agent-specificconflagration guides.

b. Issue an ETE QUIESCE command to stop ETE. (See “ETE QUIESCE” on page 25 for details.)2. Customize the ETE startup JCL

The sample ETE startup JCL is named CANSETE. It is generated by the Configuration Tool when youconfigure ETE. Use this statement to control the monitoring of LU type 1 and 3 devices and ETEresponse to non-data flow control response units (RUs) issued by such programs as DB2®. This is theformat for the EXEC statement:EXEC PGM=KETESTRN,TIME=&tme PARM= ’pppppp ,CIHT=nnnnn’

Where:

TIME=&tmeIs an optional parameter used to specify the maximum amount of time in minutes that a jobstep may use the processor or to find out through messages how much processor time a stepused.

Use the TIME parameter to increase or decrease the amount of processor time available to ajob step over the default value. A step that exceeds its allotted time abnormally terminatesand causes the job to terminate, unless an installation exit routine extends the time for the job.The exit routine IEFUTL is established through System Management Facilities (SMF). If youspecify TIME=1440, the procedure never times out.

pppppp Is the control option parameter, one or more of the following, separated by commas:

NFDRNL2Monitor, but do not force DR on LU type 1 and 3 devices (default).

This option allows collection of byte count information but not response time data forLU type 1 and 3 devices (unless the session is using DR of its own accord).


FDRNL2Monitor and force DR on LU type 1 and 3 devices. This option allows collection ofbyte count information and response time data for LU type 1 and 3 devices. Do notuse this option with 3816 or 3820 printers.

FAILNL2Fail monitor requests for LU type 1 and 3 devices.

This option prevents collection of both byte count information and response time datafor LU type 1 and 3 devices.

NFNDFC=NOForces definite response for non-data flow control response units (RUs).,

This option enables ETE to force definite response for non-data flow control RUs.Change this parameter to NFNDFC=YES to prevent the ETE subsystem from forcingdefinite response for non-data flow control RUs. You might want to code NFNDFC=YESif you experience failures in DB2 conversations such as when an SQL query passed toa DB2 application fails because the ETE subsystem has modified the response unit(RU) to force a definite response for a non-data flow control RU. Similarly, CICS mayfail with the 0813 sense code for a BID bracket error. Again, coding NFNDFC=YES mightfix this problem.

Refer to “Definite response unit failures in VTAM, DB2, and CICS” on page 38 forinformation about identifying this DB2 error.

Note: Regardless of the start parameter you use, it is recommended that ETE bestarted only once for the life of the IPL. Users of ETE services must be able to accesscontrol blocks maintained by ETE. If ETE is not available continuously, users of itsservices may suffer abends at termination such as ABENDSA03. If it becomesnecessary for ETE to be stopped prior to an IPL, STOP all users of ETE services beforestopping the ETE started task.

nnnnn CIHT table size for CICS definite response. (Chapter 9, “Using the CICS definite response,” onpage 31).

Here is an example of this startup command:EXEC PGM=KETESTRN,TIME=&TME,PARM=’,NFNDFC=YES’

3. Add the RKANPARU dataset to the ETE startup JCL.To enable or disable other control options for the ETE address space, add the RKANPARU dataset tothe ETE startup JCL. See Chapter 8, “Creating a device exclusion list,” on page 29.Add the following statement directly after the EXEC PGM=KETESTRN statement://RKANPARU DD DSN=hilev.RKANPAR,DISP=SHR

The RKANPARU dataset is where you specify information about enabling and disabling controloptions.If you do not add the RKANPARU dataset to the ETE startup JCL, no additional startup options(other than those on the EXEC statement) are processed.You must also exclude devices that cannot tolerate definite response protocol. To exclude devices thatcannot tolerate definite response protocol from ETE monitoring, complete the following steps:a. Create member KETXDLDR in the RKANPARU library.b. In member KETXDLDR, list the devices to exclude. You can refer to member KETXDLDR in the

TKANSAM dataset which contains a sample device exclusion list.c. Ensure that the ddname RKANPARU is included in the ETE JCL.See Chapter 8, “Creating a device exclusion list,” on page 29 for more information about excluding LUnames from ETE monitoring.

4. Check the TIME parameter on the JOB statement.


The sample ETE started task JCL is shipped without a TIME parameter on the JOB statement. Manysites maintain a default TIME parameter value (such as 1439 or 1440) that prevents started tasks fromtiming out. If your site's default TIME parameter value allows timeout, be sure to add an appropriateTIME parameter to the ETE JOB statement. The ETE started task must not timeout.ETE modifies the definite response bit so that it can calculate the response times for monitoredterminals. The exclusion list tells ETE what not to monitor. If you have applications that are sensitiveto definite response, use the ETE exclusion list to prevent any issues caused by ETE modifying thedefinite response bit.

5. Start ETE.Attention: Before you start ETE, ensure that you have met these prerequisites:a. Plan on running only one instance of ETE, regardless of the number of OMEGAMON XE

monitoring agents or sessions are using ETE.b. Ensure that VTAM is active.c. Because ETE must be active before OMEGAMON can use it, plan to start ETE as soon as possible

after VTAM initializes. If any sessions were started before ETE startup, those terminals' bindinginformation are unavailable to ETE. This limits ETE's effectiveness for those terminals.

d. ETE requires the VTAM internal trace to be running. ETE starts the trace automatically.e. Verify that the STEPLIB DD statement in your OMEGAMON product JCL procedure points to the

IBM Tivoli OMEGAMON product runtime load library, RKANMODU, and is APF-authorized.f. If you need to run concurrent versions of ETE during an upgrade transition period, read Chapter 4,

“Running multiple copies of ETE,” on page 13 before starting ETE.

To start ETE, issue this command at the z/OS operator console:S CANSETE

Where CANSETE is the name of the ETE address space JCL procedure.This command results in the ETE Version 6.2.0 address space remaining active until it is QUIESCEd.To verify that ETE started successfully, look for this message on the operator console or in the MVS™

syslog:ETE0091 ETE VERSION 620 SUCCESSFULLY INITIALIZED

6. Verify that ETE has started correctly.At a z/OS console, enter the ETE USERS command to verify that ETE started. Check the commandoutput that is displayed as shown in Figure 2

The first line of console output showsv ETE version numberv Subsystem identifier (00 is the default)v Load library from which you installed ETE

The ETE started task name is displayed several times because ETE is a user of its own internalservices.

ETE USERSETE0002: ETE V620 #00 LOAD DSN=hilev.RKANMODETE0040: JOBNAME ASID TCB TYPEETE0041: USER001 00176 007BE458 RSPTIMEETE0041: ETE620 00175 007EDB80 CAPTUREETE0041: ETE620 00175 007EF1F8 CAPTUREETE0041: ETE620 00175 007EF1F8 CAPTUREETE0003: COMPLETE

Figure 2. ETE USERS command output

Chapter 3. Starting ETE 9

7. Make ETE available to the OMEGAMON XE monitoring agents. To make ETE available to theOMEGAMON XE monitoring agents, you must set up all of your monitoring agents to load ETEmodules from the hilev.RKANMODU library. hilev was defined during installation, as described inyour OMEGAMON installation documentation.a. Ensure that the IBM Tivoli product load library, RKANMODU, is included in a STEPLIB DD

statement for each of your OMEGAMON jobs and started tasks. This library containsOMEGAMON and ETE load modules.

b. Ensure that all libraries in the STEPLIB concatenation are APF-authorized.8. Verify ETE and OMEGAMON operation. To verify that ETE and your OMEGAMON XE monitoring

agents are working correctly, complete the following steps:a. Start every OMEGAMON monitoring agent that uses ETE.b. Verify ETE operation by starting response time monitoring for each OMEGAMON monitoring

agent that is using ETE.

Stopping ETEETE should run continuously but can be stopped with the ETE QUIESCE command.

About this task

Keep ETE running continuously to collect session information history. If you decide to stop ETE for anyreason, do the following:

Procedure

Issue the ETE QUIESCE command as described in “ETE QUIESCE” on page 25.

Recycling a major nodeETE must be quiesced and restarted if a VTAM major node monitored by OMEGAMON II for CICS orIMS is recycled.

About this task

If a VTAM major node containing logical units that are being monitored by OMEGAMON II® for CICS orOMEGAMON II for IMS is recycled, you must quiesce ETE and restart it in order to re-establish linkage.

OMEGAMON II for MVS and OMEGAMON II for Mainframe Networks are not affected by the recycleand do not need to re-establish linkage.

Recycling ETEIf you must recycle ETE, do no delete what seems to be leftover storage in the CSA. It is reaccessed.

About this task

Keep ETE running for the life of the run. However, if you take down ETE, you may notice that somestorage is left in the CSA. Do not delete this data because it is reaccessed by ETE when the component isrestarted.

Customizing for a multi-session manager productMulti-session manager products require configuration before they can be used to obtain response times.


About this task

To obtain response time for sessions controlled by a multi-session manager product, you must configurethe multi-session manager product to produce the session switch message. For more information, seeChapter 5, “Customizing ETE to work with a multi-session manager,” on page 15,

Determining which products are using ETE servicesThe ETE USER and ETE USER=jobname commands can be used together to determine which productsare using ETE services.

About this task

There is no single command for determining which products are using ETE services, but you can makethis determination using the ETE USER and ETE USER=jobname commands.

Procedure1. Issue the ETE USER command to show who the users of ETE services are. In the example below, jobs

V410ON (OMEGAMON II for Mainframe Networks) and V410ETE (ETE itself) are users of ETEservices, though the users could be any of the OMEGAMON monitoring agents that use ETE services:- 11.32.39 NMPIPL27 ete users- 11.32.39 NMPIPL27 ETE0002: ETE V550 #00 LOAD- DSN=MFN.V4R1M0.RKANMOD- 11.32.39 NMPIPL27 ETE0040: JOBNAME ASID TCB TYPE- 11.32.39 NMPIPL27 ETE0041: V410ON 00052 006DC0E0 RSPTIME- 11.32.39 NMPIPL27 ETE0041: V410ON 00052 006DC0E0 CAPTURE- 11.32.39 NMPIPL27 ETE0041: V410ETE 00024 006DF6A8 CAPTURE- 11.32.39 NMPIPL27 ETE0041: V410ETE 00024 006DFE88 CAPTURE- 11.32.39 NMPIPL27 ETE0041: V410ETE 00024 006DFE88 CAPTURE- 11.32.39 NMPIPL27 ETE0003: COMPLETE

2. Use the information returned in the JOBNAME field to issue a second command for details about aspecific job: ETE USER=jobname, where jobname is one of the jobnames returned by the ETE USERcommand. For example, the ETE USER=v410on command returns the following details about theV410on job:- 11.44.36 NMPIPL27 ete user=v410on- 11.44.36 NMPIPL27 ETE0002: ETE V550 #00 LOAD- DSN=MFN.V4R1M0.RKANMOD- 11.44.36 NMPIPL27 ETE0043: V410ON : ASCB=00FC7A00,- TCB=006DC0E0- 11.44.36 NMPIPL27 ETE0044: NTCP0001/NT9DT002 NTCP0002/NT9DT003- NTCP0003/NT9DT004- 11.44.36 NMPIPL27 ETE0044: NTCP0004/NT9DT005 NTCP0005/NT9DT006- NTCP0006/NT9DT007- 11.44.36 NMPIPL27 ETE0044: NTCP0007/NT9DT008 NTCP0008/NT9DT009- 11.44.36 NMPIPL27 ETE0003: COMPLETE

Chapter 3. Starting ETE 11

Chapter 4. Running multiple copies of ETE

Running multiple copies of ETE is supported in some instances, but you should be aware of theseconsiderations.

About this task

Under normal conditions, running multiple OMEGAMON XE monitoring agents requires only one copyof ETE. During test, product migration, or under special circumstances, you may need to start severalcopies of ETE Version 6.2.0 or Version 6.2.0 and prior releases.

This section describes considerations for running multiple copies of ETE. You can run any of thefollowing configurations:v Multiple copies of ETE Version 6.2.0v Multiple copies of a prior ETE releasev Version 6.2.0 and a prior ETE release

When using multiple copies, to identify and run a specific copy of ETE version 6.2.0 you must completethe following steps.

Procedure1. Include DDNAME statements to identify ETE subsystems

When using multiple copies of ETE, run the following command g to identify and run a specific copyof ETE Version 6.2.0. You must include the following DD statement in each ETE PROC://RKETVTnn DD DUMMY

Where nn is a unique numeric suffix between 00 and 15, identifying the subsystem. A maximum offour ETE address spaces can run concurrently in a single domain.

Attention: To identify the ETE subsystem to the OMEGAMON monitoring agent that is using it, besure to also include the DD DUMMY statement, as described previously, in the OMEGAMON PROC.

2. Issue the ETE command with multiples instances of ETE running.To direct ETE commands to the correct ETE when more than one ETE system is running, include theversion number in the command string, using the following command syntax:ETEnnn:cccccccc

Where nnn is the three-digit ETE version number or two-digit subsystem identifier and cccccccc is thecommand you are issuing.For example, to QUIESCE ETE Version 6.2.0, issue this command:ETE620 QUIESCE

3. If you want to run ETE with IBM Tivoli NetView® Performance Monitor, there are special operationalconsiderations when running concurrent ETEs and the IBM Tivoli NetView Performance Monitor(NPM) product.v ETE can coexist with NetView Performance Monitor. When NetView Performance Monitor starts, it

disregards any existing interface participant and installs itself as the only front-end interface toVTAM. This disables ETE operation. ETE detects this condition and reinstalls itself in conjunctionwith NPM.

v When NetView Performance Monitor stops, it removes itself as an interface participant but does notensure the integrity of other interface participants. ETE also detects this condition and recoversfrom it.


v If NetView Performance Monitor starts or stops when more than one ETE system is running, onlyone ETE recovers. The ETE that recovers depends on various factors at the time the event occurs.The ETE that does not recover does not have an impact on the system, but does not report responsetime information.

Note: Running multiple copies of ETE with NetView Performance Monitor in your productionenvironment is not recommended because of the limitations stated previously.


Chapter 5. Customizing ETE to work with a multi-sessionmanager

Understand how ETE interacts with a multi-system manager (MSM) product and follow the guidelinesfor operating with an MSM product.

This section describes how ETE interacts with multi-session managers (MSMs).

MSM overview

In a configuration with an MSM, such as IBM CL/SUPERSESSION, a terminal user logs onto the MSMusing a real terminal. Then, using a pool of Virtual Logical Unit (VLU) names, the MSM establishessessions on behalf of that real terminal.

Depending on the MSM implementation, you can use the following VLU configurations to supportmultiple logical unit-logical unit (LU-LU) sessions:v The MSM establishes multiple sessions on behalf of a real terminal using a single VLU, as shown in

the following figure:

v The MSM establishes multiple sessions on behalf of a real terminal using multiple VLUs, as shown inthe following figure:

Figure 3. MSM configuration: real terminal using a single VLU


v The MSM establishes multiple sessions on behalf of multiple real terminals using a single VLU, asshown in the following figure:

In each of the preceding configurations, ETE Version 6.2.0 measures the host and network components ofresponse time in one of the following two ways:v As host response time, the time it takes for the data to flow between the application (CICSA, CICSB,

TSO) and the VLU.v As network response time, the time it takes for the data to flow between the MSM and the real

terminals (TERMA, TERMB).

Operating ETE with MSMs

The following conventions apply to ETE operation with MSMs:v Both ETE and the MSM must be located in the same VTAM domain.v ETE supports MSMs that use the virtual session switching convention proposed by Computer

Associates International. MSMs that follow this convention produce a non-display 3270 data streammessage that is sent to the physical terminal each time a session switch is performed. This is thesession switch message. Many MSMs (including the IBM CL/SUPERSESSION product), support thisconvention. There is typically an exit program for the MSM that must be enabled in order to supportthe virtual session switching convention.

Figure 4. MSM configuration: real terminal using a multiple VLUs

Figure 5. MSM configuration: multiple real terminals using a single VLU


v When using ETE through OMEGAMON II for Mainframe Networks, the actual PLU of the virtualsession (such as CICS, IMS, or TSO) can be the same domain, across domains, or even across networks.

v You must start ETE prior to any MSM containing virtual logical units (VLUs) that ETE will monitor.ETE does not monitor MSM sessions if it is unaware of the VLU and real terminal relationship. If youcancel or stop the ETE address space, response time numbers are no longer accurate and subsequentattempts to monitor terminals might fail until the next restart of the MSM.

v The path information units (PIUs) for the session switch datastream do not travel across domains.Therefore VLUs that establish a TSO session on an LPAR other than the LPAR on which the MSM isrunning will not be monitored by the ETE that is running in the LPAR in which the TSO session isestablished.

Chapter 5. Customizing ETE to work with a multi-session manager 17

Chapter 6. Customizing ETE to work with a multi-sessionmanager

Understand how ETE interacts with a multi-system manager (MSM) product and follow the guidelinesfor operating with an MSM product.

This section describes how ETE interacts with multi-session managers (MSMs).

MSM overview

In a configuration with an MSM, such as IBM CL/SUPERSESSION, a terminal user logs onto the MSMusing a real terminal. Then, using a pool of Virtual Logical Unit (VLU) names, the MSM establishessessions on behalf of that real terminal.

Depending on the MSM implementation, you can use the following VLU configurations to supportmultiple logical unit-logical unit (LU-LU) sessions:v The MSM establishes multiple sessions on behalf of a real terminal using a single VLU, as shown in

the following figure:

v The MSM establishes multiple sessions on behalf of a real terminal using multiple VLUs, as shown inthe following figure:

Figure 6. MSM configuration: real terminal using a single VLU


v The MSM establishes multiple sessions on behalf of multiple real terminals using a single VLU, asshown in the following figure:

In each of the preceding configurations, ETE Version 6.2.0 measures the host and network components ofresponse time in one of the following two ways:v As host response time, the time it takes for the data to flow between the application (CICSA, CICSB,

TSO) and the VLU.v As network response time, the time it takes for the data to flow between the MSM and the real

terminals (TERMA, TERMB).

Operating ETE with MSMs

The following conventions apply to ETE operation with MSMs:v Both ETE and the MSM must be located in the same VTAM domain.v ETE supports MSMs that use the virtual session switching convention proposed by Computer


Figure 7. MSM configuration: real terminal using a multiple VLUs

Figure 8. MSM configuration: multiple real terminals using a single VLU


v When using ETE through OMEGAMON II for Mainframe Networks, the actual PLU of the virtualsession (such as CICS, IMS, or TSO) can be the same domain, across domains, or even across networks.

v You must start ETE prior to any MSM containing virtual logical units (VLUs) that ETE will monitor.ETE does not monitor MSM sessions if it is unaware of the VLU and real terminal relationship. If youcancel or stop the ETE address space, response time numbers are no longer accurate and subsequentattempts to monitor terminals might fail until the next restart of the MSM.

v The path information units (PIUs) for the session switch datastream do not travel across domains.Therefore VLUs that establish a TSO session on an LPAR other than the LPAR on which the MSM isrunning will not be monitored by the ETE that is running in the LPAR in which the TSO session isestablished.

Chapter 6. Customizing ETE to work with a multi-session manager 21

Chapter 7. ETE commands

The syntax for ETE operator commands is found in this section.

This chapter describes the ETE operator command. The command syntax is defined, all commandarguments are listed alphabetically with a brief description of their function, and the resulting consoleoutput is illustrated.

ETE command syntaxUse this information to understand the syntax of an ETE operator command.

Issue the ETE operator console command using the following syntax:ETEnnn cccccccc

Where:

nnn Is the three-digit ETE version number (such as 620) or two-digit ETE subsystem identifier (aunique number between 00 and 15). This suffix is only required when running multiple copies ofETE. For more information, see Chapter 4, “Running multiple copies of ETE,” on page 13.

ccccccccIs the ETE command argument

ETE accepts the ETE operator console command with an argument. The ETE command with each of itsvalid arguments is shown in the commands that follow.

ETE CLRDUMPThe ETE CLRDUMP command resets the flag that indicates dumps have been completed, which allowsadditional memory dump collection.v Command: ETE CLRDUMP

v Function: Resets the flag that indicates dumps have been completed, which allows additional memorydump collection.

v Sample:

ETE CLRDUMPETE0002: ETE V620 #00 LOAD DSN=hilev.RKANMODUETE0003: COMPLETE

ETE DUMPThe ETE DUMP command creates an SVC memory dump tailored for ETE problem analysis andtroubleshooting.v Command: ETE DUMP

v Function: Creates an SVC memory dump tailored for ETE problem analysis and troubleshooting.v Sample:


ETE DUMPETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0010: OMEGAMON SCHEDULED CSA DUMP IN PROGRESSETE0011: OMEGAMON SCHEDULED CSA DUMP COMPLETEETE0003: COMPLETE

ETE DUMPDXLThe ETE DUMPDXL command displays the excluded devices.v Command: ETE DUMPDXL

v Function: Displays the excluded devices.v Sample:

ETE DUMPDXLETE0002: ETE V620 #00 LOAD DSN=hilev.RKANMODUETE0209: DXLHTE=014A70A8 SLUNAME=DUMMYAETE0209: DXLHTE=014A7980 SLUNAME=DUMMYBETE0003: COMPLETE

ETE HELPThe ETE HELP command displays available ETE subsystem command arguments.v Command: ETE HELP

v Function: Displays available ETE subsystem command arguments.v Sample:

ETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0070: THE FOLLOWING ETE COMMANDS ARE AVAILABLE:ETE0071: CLRDUMP -- RESET DUMP FLAG/ALLOW NEW DUMPETE0071: DUMP -- PRODUCE A DIAGNOSTIC ETE SVC DUMPETE0071: DUMPDXL -- LIST EXCLUDED DEVICESETE0071: HELP -- PRODUCE THIS DISPLAYETE0071: QUIESCE -- TERMINATE THE ETE SUBSYSTEMETE0071: RESET -- RESET ETE SUBSYSTEM AND QUIESCEETE0071: SYSTEMS -- DISPLAY ETE SUBSYSTEM INSTALLEDETE0071: TRACEON -- START ETE DIAGNOSTIC TRACEETE0071: TRACEOFF -- STOP ETE DIAGNOSTIC TRACEETE0071: USER= -- DISPLAY LUNAMES MONITORED BY A SPECIFIC PRODUCTETE0071: USERS -- DISPLAY PRODUCTS USING THE ETE SUBSYSTEMETE0071: VERBOSE -- PRODUCE A DIAGNOSTIC WTO FOR SELECTED EVENTSETE0071: NOVERBOSE -- CANCEL EFFECTS OF VERBOSE COMMANDETE0003: COMPLETE

ETE NOVERBOSEThe ETE NOVERBOSE command cancels the effect of the ETE VERBOSE command. VERBOSE MODEOFF is the default status.v Command: ETE NOVERBOSE

v Function: Cancels the effect of the ETE VERBOSE command. VERBOSE MODE OFF is the defaultstatus.

v Sample:


ETE NOVERBOSEETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0003: COMPLETE.RKANMODUETE0016: VERBOSE MODE OFFETE0003: COMPLETE

ETE QUIESCEThe ETE QUIESCE command shuts down ETE.v Command: ETE QUIESCE

v Function: Shuts down ETE. Use this command before applying maintenance and restarting ETE. AfterETE shuts down, OMEGAMON receives a return code or sense code indicating that ETE is notoperational. QUIESCE does not impact other network monitoring components or products.Stopping the ETE address space using the MVS STOP command automatically generates an ETEQUIESCE command.CAUTION:A small amount of common storage is intentionally left behind and is re-used when ETE isrestarted. Do not free this storage with the CSA Analyzer because this is not orphaned storage.

Stop ETE only when necessary. It is best to start ETE immediately after VTAM startup and keep ETErunning continuously to collect session information history.Before stopping ETE with automation, the shutdown of OMEGAMON regions must be complete. AnABEND0C4 is issued if you fail to shut down OMEGAMON regions before issuing the ETE QUIESCEcommand. The automation procedure must check that no ETE users are active before the ETE QUIESCEis issued.

v Sample:

ETE QUIESCEETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0003: COMPLETE.RKANMODUETE0051: QUIESCE COMPLETEETE0003: COMPLETE

ETE RESETThe ETE RESET command resets VTAM interfaces and quiesces ETE subsystem and address space.v Command: ETE RESET

v Function: Use this command only at the direction of IBM Software Support.Resets VTAM interfaces and quiesces ETE subsystem and address space. ETE RESET impactsOMEGAMON and other network monitoring systems.Attention: Use this command only at the direction of IBM Software Support.

v Sample:

ETE RESETETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0003: COMPLETE.RKANMODUETE0072: SSTB SUBSYSTEM RESET SUCCESSFULETE0073: VTAM INTERFACE RESTOREDETE0003: COMPLETE

Chapter 7. ETE commands 25

ETE SYSTEMSThe ETE SYSTEMS command displays ETE subsystem status.v Command: ETE SYSTEMS

v Function: Displays ETE subsystem status.v Sample:

ETE SYSTEMSETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0030: VERSION ## CMD PREF STATUS INST TYPEETE0031: V620 00 ETE50000 ACTIVE STATICETE0003: COMPLETE

ETE TRACEOFFThe ETE TRACEOFF command stops ETE problem determination diagnostic trace.v Command: ETE TRACEOFF

v Function: Stops ETE problem determination diagnostic trace. Trace off is the default status.v Sample:

ETE TRACEOFFETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0079: ETE DIAGNOSTIC TRACE STOPPEDETE0003: COMPLETE

ETE TRACEONThe ETE TRACEON command starts ETE problem determination diagnostic trace.v Command: ETE TRACEON

v Function: Starts ETE problem determination diagnostic trace.v Sample:

ETE TRACEONETE0002: ETE V620 #00 LOADLIB=hilev.RKANMODUETE0078: ETE DIAGNOSTIC TRACE STARTEDETE0003: COMPLETE

ETE USER=useridThe ETE USER=userid command displays all LU names being monitored by the specific product usingETE.v Command: ETE USER=userid

v Function: Displays all LU names being monitored by the specific product using ETE. userid is a jobname as shown in the ETE USERS command display

v Sample:

ETE USER=USER001ETE0002: ETE V620 #00 LOAD DSN=hilev.RKANMODUETE0040: USER001 : ASCB=00EE9080, TCB=007C5458ETE0044: L0021450/TSOG0021 L0027740/SMVTAMG L0027990/RGSS001NETE0044: L613A45 /V146GTW1 L613A74 /OIVTAMG0 L615108 /SUPGATEGETE0044: L615A106/V146GTW1 L635 /TSOG0028ETE0003: COMPLETE


ETE USERSThe ETE USERS command shows the STCNAME or JES JOBNAME, ASID, and TCB address of eachproduct using ETE.v Command: ETE USERS

v Function: Shows the STCNAME or JES JOBNAME, ASID, and TCB address of each product using ETE.v Sample:

ETE USERSETE0002: ETE V620 #00 LOAD DSN=hilev.RKANMODUETE0040: JOBNAME ASID TCB TYPEETE0041: USER001 00176 007BE458 RSPTIMEETE0041: ETE620 00175 007EF1F8 CAPTUREETE0041: ETE620 00175 007EF1F8 CAPTUREETE0003: COMPLETE

Chapter 7. ETE commands 27

Chapter 8. Creating a device exclusion list

You can exclude devices from ETE monitoring using a device exclusion list.

This section describes a feature of ETE you can use to exclude devices from ETE monitoring, even thoughthey have been defined for monitoring by one or several OMEGAMON products. This exclusion takeseffect whether OMEGAMON defined specific or generic SLU devices for monitoring.

Protecting devices from DR

Although you use ETE to monitor response time for VTAM applications in session with SLU devices, youcan exclude SLU devices that are not tolerant of the definite response (DR) requests issued by ETE.

To do this, set up a device exclusion list specifying those SLUs that you want to exclude from DRrequests. The SLUs in the list are defined in the ETE component address space and are protected fromDR requests.

Defining the exclusion list

To create an exclusion list, you must create an KETXDLDR member in the RKANPARU dataset. You canrefer to the sample KETXDLDR member in the TKANSAM dataset.

Use the following syntax to define the exclusion list:

Card columns 1–71An asterisk (*) in column 1 indicates a comment line, all information on that line is ignored.

Note: An asterisk (*) in column 1 indicates a comment line. All information on a line containingas asterisk is ignored.

Rules:1. You can code more than one device on one line, separated by commas or blanks.2. Wildcards, masks, and generic device names are not supported.

See Step 3 under Chapter 3, “Starting ETE,” on page 7 for information about RKANPARU in the ETE JCL.

Exclusion list example

The following example shows how KETXDLDR excludes SLUs from monitoring by ETE.

************************************************************************00010000* MEMBER: KETXDLDR *00020000* *00030000* FUNCTION: SAMPLE DR DEVICE EXCLUSION LIST *00040000* *00050000************************************************************************00070000DEVICE01 00080000DEVICE02 DEVICE03 00081001DEVICE04,DEVICE05 00081301

Changing the exclusion list

You can change the device exclusion list in the KETXDLDR member of the RKANPARU dataset at anytime. To implement the changes, you must recycle (stop and then restart) ETE. Refer to “ETE QUIESCE”on page 25


on page 25 for information about stopping and restarting ETE.


Chapter 9. Using the CICS definite response

Use the information in this section to prevent immediate response mode protocol violations whenrunning the OMEGAMON II for CICS monitoring agent.

This section describes a feature of ETE Version 6.2.0 that prevents immediate response mode protocolviolations during CICS sessions.

To monitor response time, ETE may change an exception response to a definite response. If this responseis immediately followed by another PIU with definite response requested, the CICS session mayexperience an immediate response mode protocol violation (sense code X'200A'). By providing a CICSSEND exit, this feature ensures that the first request is answered before the second request is sent, thuspreventing CICS session termination (DFH3465).

The IBM-supplied CICS SEND exit forces definite response only when all of the following are true:v There is a last-in-chain or only-in-chain PIU.v End-of-bracket or change-direction is in effect.v The BIND image allows for DR and specifies FM profile 3.v The session is monitored by ETE running on the same host system as CICS.

CICS definite response solution providedIBM provided the following to help you construct a CICS definite response solution.

To support CICS definite response mode, IBM supplies the following:v Module KETXCOUN for the standard CICS SEND exit XZCOUTv Enabling and disabling of the CICS SEND exit in two forms:

– PLTPI/PLTSD module KETXCPLN to enable the exit at CICS startup and disable the exit at CICSshutdown

– CICS transaction KETX to directly enable or disable the exitv Parameter CIHT on the ETE EXEC statement to specify the CIHT table size

CICS definite response graphic overviewThe CICS definite response implementation is easier to understand after viewing this graphic.

Figure 9 on page 32 illustrates the ETE-CICS definite response implementation.


CICS releases supportedETE is CICS release sensitive.

Because this feature uses a CICS exit, ETE is now CICS release sensitive. ETE is supported for CICSTransaction Server Version 2.3 and higher with the CICS user exit program.

Multi-session manager considerationsThe multi-session manager product (MSM) and ETE must be in the same domain as CICS if you want touse the MSM to log onto CICS.

If you are using a multi-session manager (MSM) to log onto CICS, the MSM and ETE must be in thesame domain as CICS.

Installation considerationsConsider these issues if you are using the CICS definite response feature with ETE.

You must include the IBM Tivoli product load library, xKANMOD, in STEPLIB and xKANMODR in theDFHRPL concatenations of the CICS startup JCL.

For environments where you plan to run a mix of OMEGAMON XE version 4.2.0, version 4.1.0, andversion 3.1.0 releases on the same LPAR, install the ETE version 5.5.0 requisite APAR OA20701 in the CSIwhere version 4.1.0 or version 3.1.0 or both are installed prior to installing ETE version 6.2.0. ETE version5.5.0 APAR OA20701 is required if you plan to run mixed releases OMEGAMON agent on the sameLPAR (n, n-1, and n-2).

The OMEGAMON XE version 2.2.1 products that are included with ETE version 500 cannot communicatewith ETE Version 620. You must continue to run ETE version 500 in addition to ETE version 6.2.0 on thesame LPAR if you plan to run a mixture of version 221 agents and version 420 agents on the same LPA.

Figure 9. ETE DR Implementation for CICS


The CIHT parameter is located on the ETE EXEC statement. You may choose not to enable this feature byspecifying CIHT=0. For more information on the CIHT parameter, see “ETE EXEC Parameter CIHT” andStep 2 under Chapter 3, “Starting ETE,” on page 7.

CICS table updates requiredThese table updates are required before you can initialize ETE support components in the CICS addressspace.

Before you can initialize ETE support components in the CICS address space, you must modify sampleCSD definitions files in TKANSAM that are included with ETE. These sample jobs are found in thefollowing locations and perform the functions described in the following sections::

&thilev.TKANSAM(KETCSDJ)A sample job to update the CSD definitions.

&thilev.TKANSAM(KETCSD)The CSD Definitions to delete old versions and define the new entities.

If you prefer to use transaction CEDA to define resources online, do the following:1. Define transaction KETX with the same tranaction definitions specified in the sample CSD defintion

found in &thilev.TKANSAM(KETCSD). If you migrate resource definitions from a prior CICS release,make sure that the migrated definitions match those found in the KETCSD sample definition.

2. Define programs KETXCPLN and KETXCOUN with the same program definitions specified in thesample CSD definition found in &thilev.TKANSAM(KETCSD).

ETE EXEC Parameter CIHTUse this information to understand the syntax of the CIHT parameter in specifying an ETE table.

CIHT is the parameter on the ETE EXEC statement you use to specify the number of entries in the ETEtable, CIHT. ETE uses CIHT to monitor sessions. The syntax of the CIHT parameter is:CIHT=nnnnn

The following table shows the effects of the possible CIHT settings.

If CIHT is . . . Then CIHT . . .

Omitted Defaults to 1499

Between 0 and 99999 Is within valid range

Zero Is not allocated and CICS DR control is disabled, even if the KETXCOUN exit isenabled in the CICS address space

Between 1 and 1499 Defaults to 1499

Between 1500 and 99999 Is converted to the nearest higher prime number

Specify the following:CIHT = 2 * sessions

Where sessions is your estimate of the number of sessions monitored by ETE at any one time.

For more information about the ETE EXEC statement in the ETE startup JCL, see Step 2 under Chapter 3,“Starting ETE,” on page 7.

Chapter 9. Using the CICS definite response 33

CICS SEND exitEnable the CICS SEND exit before starting response time collection for any CICS resource.

ETE uses the standard CICS SEND exit, XZCOUT, to control DR at the end of a logical transaction. IBMsupplies the CICS exit module KETXCOUN.

You must enable this exit before starting response time collection for any CICS resource. Failure to do socan result in session termination. See “Enabling and disabling the exit using PLTPI or PLTSD” and“Enabling and disabling the exit using transaction KETX.”

The exit applies to all CICS applications using 3270 VTAM terminals. It is invoked every time a CICSSEND command is issued with only a negligible increase in instruction path length.

Enabling and disabling the exit using PLTPI or PLTSDUse this information to enable and disable the CICS SEND exit using PLTPI or PLTSD.

The enabling and disabling processor is a CICS command-level application module. After properinstallation of this feature (see “Installation considerations” on page 32 and “CICS table updatesrequired” on page 33), you can use the IBM-supplied PLTPI module KETXCPLN to automatically enablethe IBM-supplied CICS SEND exit at CICS startup. Likewise you can use the same module KETXCPLNin the PLTSD to automatically disable the exit at CICS shutdown.

Any confirmation or error messages from enabling and disabling are displayed as WTO messages on themaster console. Refer to the IBM Tivoli Monitoring and OMEGAMON Information Center athttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml tosearch all OMEGAMON messages, or the IBM Tivoli Monitoring: Messages book for explanations of ETEmessages.

Attention: This procedure just described is the preferred method for automatically enabling anddisabling the CICS SEND exit.

Enabling and disabling the exit using transaction KETXUse this information to enable and disable the CICS SEND exit using KETX.

You can also use the CICS KETX transaction to directly enable or disable the CICS SEND exit or to viewthe current status of the exit:

KETX ENABLEEnables the CICS SEND exit. The abbreviation is KETX E.

KETX DISABLEDisables the CICS SEND exit. The abbreviation is KETX D.

KETX STATUSDisplays the current status of the CICS SEND exit. The abbreviation is KETX.

KETX DIAGNOSEDisplays diagnostics if the CICS SEND exit is enabled. Use this transaction only if requested byIBM Software Support. The abbreviation is KETX DIAG.

Confirmation or error messages from KETX display at the initiating terminal. Refer to the IBM TivoliMonitoring and OMEGAMON Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml to search all OMEGAMON messages, or the IBM TivoliMonitoring: Messages book for explanations of ETE messages.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml



Chapter 10. Reporting ETE problems

Because ETE is a subsystem, the procedure for reporting problems with ETE is different from that usedfor the OMEGAMON monitoring agents.

ETE runs as a subsystem and is a bit different than the OMEGAMON monitoring products. The ETEsubsystem has hooks into the VTAM address space. When a problem occurs with ETE, the scope of theenvironment to be analyzed is larger than for most products, certainly larger than the OMEGAMON XEmonitoring agents. To debug an ETE problem, IBM Software Support needs to know about the VTAMaddress space, ETE address space, and all the OMEGAMON XE monitoring agents running on the LPARthat are using the ETE API. IBM Software Support also needs to know about any multi-session managerproducts that may be running on the LPAR.

ETE is not Tivoli Management Services/Engine (TMS/Engine)-based as monitoring agents on z/OS areand does not write to the RKLVLOG or have other debugging information available to it that theOMEGAMON monitors do.

This section contains the procedure for gathering information about certain conditions or errors requiringassistance from IBM Software Support.

Procedure for reporting a problemFollow this procedure to gather information to report an ETE problem.

About this task

Gather the following information and memory dumps before contacting IBM Software Support, whichenables IBM Software Support to assist you in a timely and efficient manner.

Have the following information and data available before contacting IBM Software Support:

Procedure1. Describe details of your system and network configurations.

Many network problems are directly related to network configuration. Since ETE is located on a host,network configuration also imposes limitations on the capability of ETE. Identify the following itemsin the problem report:a. The subarea network configuration, where the VTAMs and NCPs are located, and how they are

connected.b. The location and type of the real terminal or terminals that are involved. What is the type of the

terminal or terminals, are they locally attached, remotely attached, or ethernet? Is there amulti-session manager involved?

c. The system configuration of the products that are running:v OMEGAMON XE monitoring agentsv ETEv The IBM CL/SUPERSESSION product

Are they on the same or different z/OS systems?d. The identity of similar products by other vendors.

2. Determine the software release and maintenance levels of both IBM and other vendor products.3. Record all messages and codes.


Record ETE and OMEGAMON message numbers, return codes, and sense codes. Be sure to recordany related VTAM, CICS, IMS, TSO, or CL/SUPERSESSION error messages. If the z/OS console log,NetView for z/OS operator log, master console log, or other logs are available, include them.

4. Obtain OMEGAMON 3270 debug screens, if available.To obtain debug screens for OMEGAMON XE for z/OS or OMEGAMON XE for CICS on z/OS, enterthis OMEGAMON 3270 (Classic) INFO-line command:DEBUG

5. Save any memory dumps generated.If ETE causes a storage dump in the z/OS or VTAM subsystems or in ETE itself, save this storagedump for problem analysis.

6. Request a non-destructive storage dump of ETETo request ETE to take a non-destructive storage dump, enter this command from the z/OS systemconsole:ETE DUMP

Note: This is an ETE command, not the MVS DUMP command.7. Issue traces as directed by IBM Software Support. The following information describes the kinds of

trace data that you might be asked to provide:If you determine that the problem is related to data traffic, terminals hanging, incorrect data, or someother area of network operation, you need to create a VTAM I/O trace, a VTAM buffer trace, and ETEdiagnostic traces.a. Start GTF trace with options RNIO and USR or use the OMEGAMON II for Mainframe Networks

Internal Trace Feature. For GTF description see the IBM Diagnostics: Using Dumps and Traces (XA orESA) manual or the Diagnostics: Service Aids (370) manual. For more information on theOMEGAMON trace feature see the OMEGAMON II for Mainframe Networks User's Guide.

b. Start VTAM I/O and buffer traces. See the IBM z/OS Communications Server: Operations manual.v If the problem is related to the real terminal and the user session does not involve a

multi-session manager, request VTAM traces for the real physical terminal.v If the problem session does involve a virtual terminal, trace both the real physical terminal and

the destination host application system (such as CICS or TSO).c. Recreate the problem situation while the trace is running.d. Stop the GTF trace.e. Stop the VTAM trace.

8. Issue CICS transaction KETX DIAGNOSE.If you determine that the problem is related to CICS sessions or the IBM-supplied CICS SEND exit,issue the following transaction from a CICS terminal:KETX DIAG

The output of this transaction is routed to the master console and to the initiating terminal.

Note: This step is relevant only if you are using ETE to monitor response times of CICS transactions.If this is not the case, then this information would not be available.

9. Copy the following data to tape and send to IBM Software Support:v The portion of the master console log containing the output of transaction KETX DIAG.v The raw dump and trace data sets. Do not send formatted dumps or traces.


Chapter 11. ETE troubleshooting

Use this information to troubleshoot problems with ETE.

The following ETE and related OMEGAMON monitoring agent on z/OS troubleshooting scenarios arediscussed in this chapter:v “ABEND 0C4 received with the ETE started task”v “ABEND 0D6 when running with any OMEGAMON agent using ETE services” on page 38v “ETE address space abends with error code U0404” on page 39v “ETE message ETE0101: ETE COULD NOT BE STARTED. VTAM NOT INITIALIZED OR VTAM IS AT

AN UNSUPPORTED LEVEL logged” on page 39v “ETE storage usage is excessive” on page 39v “Multiple load attempts per day of ETE modules made trying to initialize the ETE subsystem” on page

40v “OMEGAMON II for IMS Message OEI971 EPILOG/IMS ETE INSTALL FAILED ETE IS NOT ACTIVE

logged” on page 41v “OMEGAMON II for MVS message OM8389: RTA Not Operational. RC=20 RSC=8000001E; RTA: TSO

light is blue, meaning inactive” on page 41v “OMEGAMON II for MVS message OM8389 RC=20 SC=4080012A User Already Defined logged when

ETE is restarted” on page 42v “SMP/E message GIM35908I logged when installing OMEGAMON II for CICS and OMEGAMON XE

for CICS” on page 42v “Startup request failed with message ETE0090 logged” on page 42v “Users signing on to TSO through a multi-session manager product are listed using the TSO HOST

command but not the ETE USERS command” on page 43

ABEND 0C4 received with the ETE started taskUse this troubleshooting information if you receive an ABEND 0C4 with the ETE started task.

Description of problem

A common cause of this return code on the ETE startup task is that VTAM was not completely initializedwhen ETE was started. This is a serialization problem where ETE is started before VTAM has completedinitialization. This scenario is not supported. VTAM must have completed initialization before ETE isstarted, else this abend code and perhaps others will be logged.

Resolution

To resolve this problem, start VTAM first and when VTAM has completed initialization, start ETE.

The same principle is true if you stop and re-start ETE using automation. If you automate the stoppingand starting or ETE, ensure that the previous instance of ETE has stopped completely before restarting it.One method of confirming that ETE has stopped is evidence of the $HASP395 message in the SYSLOG.


ABEND 0D6 when running with any OMEGAMON agent using ETEservicesUse this troubleshooting information if you receive an ABEND 0D6 when running any OMEGAMONagent with ETE services.


In an environment running OMEGAMON II for MVS (or any OMEGAMON II component), the ETEstarted task abended with a 0D6 return code. A typical situation that produces this error is as follows:1. The user starts ETE services.2. The user starts an OMEGAMON II component that uses ETE services.3. The user has a problem with the OMEGAMON II component that was using ETE and cancels the

OMEGAMON II component in a way that prevents cleanup of control blocks known to ETE. Thistypically happens when a user issues the MVS CANCEL command to stop an OMEGAMON IIcomponent that uses ETE services instead of the MVS STOP command.

Resolution

This abend message is associated with how the ETE started task has been stopped in previous runs.Because the ETE services require a unique PC number, it is probable that the PC number obtainedoriginally by the OMEGAMON II component (the instance that was cancelled) is no longer valid. TheLXRES macro, which is used to establish the PC number, indicates that the PC number can becomeinvalid if the cross-memory ownership task terminates. An MVS CANCEL of the OMEGAMON II componentASID ends the cross-memory ownership task.

The ETE ASID is supposed to be started once for the life of the IPL. If it needs to be stopped, use the MVSSTOP command or the ETE QUIESCE command to stop ETE. Users of ETE services must be able to accesscontrol blocks maintained by ETE. If ETE is not available continuously, users of its services may sufferabends at termination such as ABENDSA03. Keep ETE running for the life of the IPL.

To avoid the abend, stop the OMEGAMON ASID instead of cancelling it. See “ETE QUIESCE” on page25 for more information on using the ETE QUIESCE command.

Definite response unit failures in VTAM, DB2, and CICSUse this troubleshooting information to diagnose definite response unit failures in VTAM, DB2, or CICS.


Definite response unit failures can be apparent in a number of products that use ETE services, andproduct-unique situations and error codes are produced:v CICS transactions abend with message DFHZ3465I and Definite Response Protocol Violation sense

200A is written to the SYSLOG. This problem and its resulting message indicate that ETE CICS SENDexit was not implemented correctly. Refer to Chapter 9, “Using the CICS definite response,” on page 31for more information about implementing the CICS SEND exit. Another common violation is the BIDrequest that gets VTAM sense code 0813.

v DB2 message DSNL500I with sense code 40190000 is found in the SYSLOG. This message indicates afailure of a DB2 conversation. An SQL query passed to a DB2 application failed when the ETEsubsystem modified the response unit (RU) to force a definite response for a non-data flow control RU.

v Intermittent VTAM SENSE 00002022 is found in the SYSLOG. This error usually indicates that requiredmaintenance has not been applied. Check the support pages to ensure that the most recentmaintenance has been applied and that the PARM=’,NFNDFC=YES’ is being used on startup.


Resolution

To resolve these types of issues, a new keyword parameter (NFNDFC) was created to enable ETE users toconfigure ETE to control whether or not the ETE subsystem forces definite response for non-data flowcontrol RUs. The default is NFNDFC=NO. See Step 2 under Chapter 3, “Starting ETE,” on page 7 for moreinformation.

Refer to Step 2 under Chapter 3, “Starting ETE,” on page 7 for information about how to code this parmstatement and for other positional and keyword parameters for the ETE product.

ETE address space abends with error code U0404Use this troubleshooting information if the ETE address space abends and you see error code U0404.


The ETE address space abends with a U0404 error code, indicating that the VTAM internal traceoperation has stopped. ETE requires that VTAM internal trace be running.

Resolution

To address this issue, determine what is stopping the VTAM Internal Trace - PIU Trace shortly before theabend. Trace may be stopped by an operator issuing a command such as this one:F NET,NOTRACE,ALL

Or by automation or another software product performing the same action evidenced in the command.The command should not be issued while ETE is active, because the product was designed to abend witha U0404 if VTAM Internal Trace - PIU Trace is stopped.

ETE message ETE0101: ETE COULD NOT BE STARTED. VTAM NOTINITIALIZED OR VTAM IS AT AN UNSUPPORTED LEVEL loggedUse this troubleshooting information if you find ETE message ETE0101 in the ETE log.


You find this message in your ETE log:ETE COULD NOT BE STARTED. VTAM NOT INITIALIZED OR VTAM IS AT AN UNSUPPORTED LEVEL.

Resolution

You have not applied maintenance that supports the level of z/OS (VTAM) on which you are trying torun. Ensure that when you upgrade your z/OS level, you apply an appropriate currency PTF so that ETEwill run under the new level of z/OS.

ETE storage usage is excessiveUse this troubleshooting information if you consider that storage usage by ETE is excessive.


In some instances, you may consider that ETE is using too much storage.

Chapter 11. ETE troubleshooting 39

Resolution

While full performance data for performing storage calculations is not available, storage analysis for asample set of resources being monitored by ETE has been conducted, based on the filters one ETE userprovided. Storage dumps were analyzed and the following analysis was created.

In a typical ETE environment, there were several programmatic users of ETE services:v OMEGM2RCv OMEGCMSv OMEGNETv OMEGETE (OMEGETE, the ETE task, is a also user of ETE services)

ECSA Storage: The greatest use of common storage was for ECSA. Though ETE requires the use of ESQAtoo, ECSA is used in the greatest quantity. There is a certain amount of ECSA storage that ETE requiresfor startup; this startup storage includes storage for modules and control blocks. Some of the controlblocks (such as the CUWX) vary in size. The slot size and number of slots for this control block aredependent on the VTAM I/O buffer size defined. This control block can be expanded (chained) as thenumber of monitored sessions increases. In large networks, these chains can grow quite large. Forexample, chained CIHT control blocks have been observed that are over 6K in size and hold the hashedVTAM CID value for each unique session.

ECSA Storage: The difficulty in calculating an exact number of ECSA bytes per session monitored stemsfrom the fact that certain control blocks must be expanded when they become full in order to monitoradditional sessions. For example, if 100 sessions are being monitored and the 101st session causes anexpansion of a control block, the storage needs can be misleading. A conservative estimate for thenumber of ECSA bytes needed per session monitored is 500 bytes, depending on the setting you havedefined for the VTAM I/O buffer. If more than one user is monitoring the same sessions, then storagerequirements increase for each user. When users monitor the same sessions, the storage requirement foran additional user is slightly less than that of the first because some control blocks are shared. Thedifference is negligible, however, so a good estimate is that each user requires 500 bytes per sessionmonitored. Naming of resources also affects the amount of storage required. If the filters that define thenames of the resources being monitored are specific, ETE and its users requires less storage. For example,if you specified ZAP* instead of Z* to satisfy the criteria for resources to be monitored, less storagewould be required.

Multiple load attempts per day of ETE modules made trying to initializethe ETE subsystemUse this troubleshooting information if you find that multiple load attempts of ETE modules are beingperformed in an attempt to initialize the ETE subsystem when the ETE started task is no running.


Multiple loads per day of ETE modules are being performed in an attempt to initialize the ETEsubsystem when the ETE started task was not running.

Resolution

In this situation, the user had configured runtime environment (RTE) for the OMEGAMON II monitoringagent to use the ETE subsystem to gather TSO response time data, but subsequently decided not to usethe ETE product. The ETE subsystem was not running but z/OS periodically made calls to try andregister with the ETE subsystem. These attempts resulted in redundant loads of ETE modules.


To address this situation, start the ETE subsystem so that the z/OS product may register with ETE. Thecode will be loaded for the initial registration with the ETE subsystem, but as registration will besuccessful, the code will not be deleted. Therefore no further loads will be necessary.

The problem has been reported with OMEGAMON II for MVS but might also occur with other agents.

OMEGAMON II for IMS Message OEI971 EPILOG/IMS ETE INSTALLFAILED ETE IS NOT ACTIVE loggedUse this troubleshooting information if you find IMS Message OEI971 logged.


You see OMEGAMON II for IMS message OEI971 logged::EPILOG/IMS ETE INSTALL FAILED. ETE IS NOT ACTIVE.

Resolution

The following scenarios might cause this error message to be displayed.1. ETE is not active.2. The OMEGAMON II for IMS Monitoring agent is trying to connect to an address space where an

unsupported level of ETE is running. This happens, for example, when an ETE address space is activeand OMEGAMON II for IMS tries to connect to an ETE address space.

3. The OMEGAMON II for IMS address space includes a //RKETVTnn DD card, and the ETE addressspace has no such DD card or the suffixes of the two cards are different.

4. Some combination of Points 2 and 3. OMEGAMON II for IMS can connect to an ETE address spaceonly if the //RKETVTnn DD cards match (or there no such DD cards) and the versions of ETE andOMEGAMON II for IMS are the same (Version 500 and later only).

This situation is most likely to occur when you have multiple instances of ETE running, and assigned todifferent OMEGAMON II components using DD card entries. For more information, see Chapter 4,“Running multiple copies of ETE,” on page 13.

OMEGAMON II for MVS message OM8389: RTA Not Operational. RC=20RSC=8000001E; RTA: TSO light is blue, meaning inactiveUse this troubleshooting information if you receive message OM8389 from OMEGAMON II for MVS.


You find OMEGAMON II for MVS message OM8389 logged:OM8389: RTA Not Operational. RC=20 RSC=8000001E; RTA: TSO light isblue, meaning inactive

Resolution

Two situations are known to cause this problem:v The ETE address space is not active.v ETE and the ETE user have not specified the same ETE subsystem number in the started task. The ETE

subsystem number may be defined with the RKETVTnn DD card in the format://RKETVTnn DD Dummy


Where nn is a numeric suffix between 00 and 15 indicating the subsystem number that you want toconnect to. The default for the ETE collector address space is 00 (//RKETVT00 DD DUMMY). The collectoraddress space cannot find ETE, if these DD cards are different.

It is also been noted that the TSO RTA light may not reflect actual users because the message 'NOTUSING AN SNA TERMINAL' is issued if users are logging on with a multi-session manager productsand ETE has not been configured to work with it. For more information, see Chapter 5, “CustomizingETE to work with a multi-session manager,” on page 15 and Chapter 4, “Running multiple copies ofETE,” on page 13.

OMEGAMON II for MVS message OM8389 RC=20 SC=4080012A UserAlready Defined logged when ETE is restarted

When the ETE address space is restarted, this message is logged:OM8389 RC=20 SC=4080012A User Already Defined

To address this issue, add the following DD statement to the ETE startup JCL, as well as the startup JCLfor the OMEGAMON II component started tasks that connect to ETE, such as OMIIRCOL and KOCCI://RKETVT01 DD DUMMY

Restart the ETE started task, and, if necessary, recycle the OMEGAMON XE monitoring agents on z/OSthat connect to ETE. Loading the initial program on the affected system or LPAR also fixes the problem.

For more information, see Chapter 4, “Running multiple copies of ETE,” on page 13.

SMP/E message GIM35908I logged when installing OMEGAMON II forCICS and OMEGAMON XE for CICSUse this troubleshooting information if you find SMP/E message GIM35908I logged when installingOMEGAMON II for CICS or OMEGAMON XE for CICS.


OMEGAMON II for CICS and OMEGAMON XE CICS were installed into a new GLOBAL CSI, but theCSI receives message GIM35908I COREQUISITE SYSMOD nn WAS MISSING, where nn is the identifier for theOMEGAMON XE monitoring agents.

Resolution

This message indicates that the OMEGAMON components were installed out of sequence. Install andconfigure the OMEGAMON BASE (and ETE) products in sequence before installing OMEGAMON XE forCICS and OMEGAMON II for CICS.

Startup request failed with message ETE0090 loggedUse this troubleshooting information if you find ETE message ETE0090 logged when a startup requesthas failed.


During startup of ETE, the following error is found in the ETE log:ETE0090: ETE STARTUP INSTALL REQUEST FAILED: RC=80FCDE9A, SC= 00000000


Resolution

The usual cause of this problem is that ETE was not shut down cleanly (for example, the MVS CANCELcommand was used instead of the ETE QUIESCE command). In such a case, control blocks or storageassociated with ETE are orphaned in z/OS common storage. When you try to re-start ETE withoutreloadng the initial program on the affected system, the corrupted control blocks might prevent ETE fromstarting. Issuing an MVS STOP against the ETE address space and then issuing a MVS START for the ETEaddress space after it comes down should prevent this problem.

Users signing on to TSO through a multi-session manager product arelisted using the TSO HOST command but not the ETE USERScommandUse this troubleshooting information if you logged onto TSO through a multi-session manager and didnot find your user ID listed when you used the ETE USERS command.


Users who signed into TSO through a multi-session manager product can be displayed using the TSOHOST command but cannot be displayed using the ETE USERS command.

Resolution

For TSO users of multi-session manager products to be displayed in ETE, these rules must be followed.1. Both ETE and the MSM must be located in the same VTAM domain.2. ETE supports MSMs that use the virtual session switching convention proposed by Computer


3. You must start ETE prior to any MSM containing virtual logical units (VLUs) that ETE will monitor.ETE does not monitor MSM sessions if it is unaware of the VLU and real terminal relationship. If youcancel or stop the ETE address space, response time numbers are no longer accurate and subsequentattempts to monitor terminals might fail until the next restart of the MSM.

4. The path information units (PIUs) for the session switch datastream do not travel across domains.Therefore VLUs that establish a TSO session on an LPAR other than the LPAR on which the MSM isrunning will not be monitored by the ETE that is running in the LPAR in which the TSO session isestablished.

See Chapter 5, “Customizing ETE to work with a multi-session manager,” on page 15 for additionalinformation on this topic.


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 Monitoring Server.

These publications are listed in the following categories:v IBM Tivoli OMEGAON XE for Mainframe Networks and OMEGAMON II for Mainframe Networks

publicationsv IBM Tivoli Monitoring libraryv Related publications

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/index.jsp. To open the Documentation Guide in the information center, select Using thepublication in the Contents pane. To find a list of new and changed publications, click What's new onthe Welcome page of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. To findpublications from the previous version of a product, click Previous information centers on the Welcomepage for the product.

IBM Tivoli OMEGAMON XE for Mainframe Networks publicationsThe following publications provide information common to the OMEGAMON XE products.v IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide, SC27-2384-03

Summarizes the planning and configuration tasks for the OMEGAMON XE for Mainframe Networksand the OMEGAMON II for Mainframe Networks monitoring agents.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference, SC27-2894-01Provides a reference guide for using the PARMLIB method of installation to configure OMEGAMONXE for Mainframe Networks and the OMEGAMON II for Mainframe Networks monitoring agents.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: User's Guide, SC27-2383-03Introduces the features, workspaces, attributes, and predefined situations for the OMEGAMON XE forMainframe Networks product and supplements the user assistance provided with this product. Thisdocument is written for network operators.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide, GC27-2385-03,Provides explanations for the messages issued by the OMEGAMON XE for Mainframe Networksproduct, OMEGAMON II for Mainframe Networks component, and problem determinationinformation.

v OMEGAMON II for Mainframe Networks: User's Guide, GC32-9274-00,Provides information about using the OMEGAMON II CUA interface to monitor the SNA elements inyour network and tune VTAM, your NCPs and the PUs and LUs connected to them.

v OMEGAMON II for Mainframe Networks: Historical Reporting Guide, GC32-9272-00Describes how to produce reports or graphs of network usage and activity over selected time periods.This book explains how to use the SMF records created by OMEGAMON II for Mainframe Networksto produce reports and graphs with SAS and view SAS graphs. It also describes the SAS samplereports that the product provides. This book is intended for a network performance analyst, networkcapacity planner, or network designer.

v OMEGAMON II for Mainframe Networks: NCP Monitoring Guide, GC32-9273-00


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


Explains how to use the NCP Monitor component of OMEGAMON II for Mainframe Networks tomonitor and tune your network, including your NCPs and the PUs and LUs connected to them. Thisguide also describes how to set NCP monitoring options and thresholds.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring and about the commonlyshared components of Tivoli Management Services:v Quick Start Guide, GI11-8058

Introduces the components of IBM Tivoli Monitoring.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-4105Gives instructions for the SMP/E installation of the Tivoli Management Services components on z/OS.

v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC32-9463Gives detailed instructions forusing the Configuration Tool to configure Tivoli Enterprise Monitoring Server on z/OS systems.Includes scenarios for using batch mode to replicate monitoring environments across the z/OSenterprise. Also provides instructions for setting up security and for adding application support to aTivoli Enterprise Monitoring Server on z/OS.

v Administrator's Guide, SC32-9408Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v High-Availability Guide for Distributed Systems, SC23-9768Gives instructions for several methods of ensuring the availability of the IBM Tivoli Monitoringcomponents.

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 Tivoli Enterprise Portal User's Guide, SC32-9409Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons anddetailed instructions for all Tivoli Enterprise Portal features.

v Command Reference, SC32-6045Provides detailed syntax and parameter information, as well as examples, for the commands you canuse in IBM Tivoli Monitoring.

v Troubleshooting Guide, GC32-9458Provides information to help you troubleshoot problems with the software.

v Messages, SC23-7969Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS andTMS:Engine).

v IBM Tivoli Universal Agent User's Guide, SC32-9459Introduces 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-9461Explains 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-1921Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

v ,Explains how to use the Performance Analyzer to understand resource consumption trends, identifyproblems, resolve problems more quickly, and predict and avoid future problems.

Documentation for the base agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents aspart of the product. If you purchased a monitoring agent product (for example, an OMEGAMON XEproduct) that includes the commonly shared components of Tivoli Management Services, you did notreceive the base agents.

The following publications provide information about using the base agents.v Operating system agents:

– Windows OS Agent User's Guide, SC32-9445– UNIX OS Agent User's Guide, SC32-9446– Linux OS Agent User's Guide, SC32-9447– i5/OS Agent User's Guide, SC32-9448– UNIX Log Agent User's Guide, SC32-9471

v Agentless operating system monitors:– Agentless Monitoring for Windows Operating Systems User's Guide, SC23-9765– Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761– Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763– Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764– Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762

v Warehouse agents:– Warehouse Summarization and Pruning Agent User's Guide, SC23-9767– Warehouse Proxy Agent User's Guide, SC23-9766

v System P agents:– AIX Premium Agent User's Guide, SA23-2237– CEC Base Agent User's Guide, SC23-5239– HMC Base Agent User's Guide, SA23-2239– VIOS Premium Agent User's Guide, SA23-2238

v Other base agents:– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490

Related publicationsYou can find useful information about related products in the IBM Tivoli Monitoring and OMEGAMONXE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp.

Other sources of documentationYou can also obtain technical documentation about IBM Tivoli Monitoring and related products from thefollowing sources:v (formerly OPAL)

http://www.ibm.com/software/brandcatalog/ismlibrary/

Documentation library 47


http://www.ibm.com/software/brandcatalog/ismlibrary/

is an online catalog that contains integration documentation and other downloadable productextensions.

v Redbookshttp://www.redbooks.ibm.com/IBM Redbooks and Redpapers include information about products from platform and solutionperspectives.

v TechnotesTechnotes provide the latest information about known product limitations and workarounds. You canfind Technotes through the IBM Software Support website at http://www.ibm.com/software/support/probsub.html, or more directly through your product website, which contains a link to Technotes(under Solve a problem).

v Tivoli wikis on the IBM developerWorks websiteTivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the homefor interactive wikis that offer best practices and scenarios for using Tivoli products. The wikis containwhite papers contributed by IBM employees, and content created by customers and business partners.Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki at http://www.ibm.com/

developerworks/wikis/display/tivolimonitoring/Home provides information about IBM TivoliMonitoring and related distributed products, including IBM Tivoli Composite ApplicationManagement products.

– Tivoli System z Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about theOMEGAMON XE products, NetView for z/OS, Tivoli Monitoring Agent for z/TPF, and otherSystem z monitoring and application management products.


http://www.redbooks.ibm.com/

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


http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home


http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides ways foryou to obtain the support you need.

OnlineThe following sites contain troubleshooting information:v Go to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html

and follow the instructions.v Go to the IBM Tivoli Distributed Monitoring and Application Management Wiki at

http://www.ibm.com/developerworks/wikis/ display/tivolimonitoring/Home. Feel free tocontribute to this wiki.

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 product's Troubleshooting Guide.

Using IBM Support AssistantThe IBM Support Assistant is a free, stand-alone application that you can install on any workstation. Youcan then enhance the application by installing product-specific plug-in modules for the IBM products youuse.

The IBM Support Assistant saves you the time it takes to search the product, support, and educationalresources. The IBM Support Assistant helps you gather support information when you need to open aproblem management record (PMR), which you can then use to track the problem.

The product-specific plug-in modules provide you with the following resources:v Support linksv Education linksv Ability to submit problem management reports

For more information, and to download the IBM Support Assistant, see http://www.ibm.com/software/support/isa. After you download and install the IBM Support Assistant, follow these steps to install theplug-in for your Tivoli product:1. Start the IBM Support Assistant application.2. Select Updater on the Welcome page.3. Select New Properties and Tools or select the New Plug-ins tab (depending on the version of IBM

Support Assistant installed).4. Under Tivoli, select your product, and then click Install. Be sure to read the license and description.

If your product is not included on the list under Tivoli, no plug-in is available yet for the product.5. Read the license and description, and click I agree.6. Restart the IBM Support Assistant.




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



Obtaining fixesA product fix might be available to resolve your problem. To determine which fixes are available for yourTivoli software product, follow these steps:1. Go to the IBM Software Support website at http://www.ibm.com/software/support.2. Under Select a brand and/or product, select Tivoli.

If you click Go, the Search within all of Tivoli support section is displayed. If you don't click Go,you see the Select a product section.

3. Select your product and click Go.4. Under Download, click the name of a fix to read its description and, optionally, to download it.

If there is no Download heading for your product, supply a search term, error code, or APAR numberin the field provided under Search Support (this product), and click Search.

For more information about the types of fixes that are available, see the IBM Software Support Handbook athttp://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html.

Receiving weekly support updatesTo receive weekly e-mail notifications about fixes and other software support news, follow these steps:1. Go to the IBM Software Support website at http://www.ibm.com/software/support.2. Click My support in the far upper-right corner of the page under Personalized support.3. If you have already registered for My support, sign in and skip to the next step. If you have not

registered, click register now. Complete the registration form using your e-mail address as your IBMID and click Submit.

4. The Edit profile tab is displayed.5. In the first list under Products, select Software. In the second list, select a product category (for

example, Systems and Asset Management). In the third list, select a product sub-category (forexample, Application Performance & Availability or Systems Performance). A list of applicableproducts is displayed.

6. Select the products for which you want to receive updates.7. Click Add products.8. After selecting all products that are of interest to you, click Subscribe to email on the Edit profile

tab.9. In the Documents list, select Software.

10. Select Please send these documents by weekly email.11. Update your e-mail address as needed.12. Select the types of documents you want to receive.13. Click Update.

If you experience problems with the My support feature, you can obtain help in one of the followingways:

OnlineSend an e-mail message to [email protected], describing your problem.

By phoneCall 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software SupportIBM Software Support provides assistance with product defects. The easiest way to obtain that assistanceis to open a PMR or ETR directly from the IBM Support Assistant.


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

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html

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

Before contacting IBM Software Support, your company must have an active IBM software maintenancecontract, and you must be authorized to submit problems to IBM. The type of software maintenancecontract that you need depends on the type of product you have:v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational

products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems),enroll in Passport Advantage in one of the following ways:

OnlineGo to the Passport Advantage website at http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm .

By phoneFor the phone number to call in your country, go to the IBM Software Support website athttp://techsupport.services.ibm.com/guides/contacts.html and click the name of yourgeographic region.

v For customers with Subscription and Support (S & S) contracts, go to the Software Service Requestwebsite at https://techsupport.services.ibm.com/ssr/login.

v For customers with Linux, iSeries, pSeries, zSeries, and other support agreements, go to the IBMSupport Line website at http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM eServer software products (including, but not limited to, DB2 and WebSphere products thatrun in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreementby working directly with an IBM sales representative or an IBM Business Partner. For more informationabout support for eServer software products, go to the IBM Technical Support Advantage website athttp://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV(1-800-426-7378) in the United States. From other countries, go to the contacts page of the IBM SoftwareSupport Handbook on the web at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html and click the name of your geographic region for phone numbers of people who providesupport for your location.

Support information 51

http://www.lotus.com/services/passport.nsf/ WebDocs/Passport_Advantage_Home

http://www.lotus.com/services/passport.nsf/ WebDocs/Passport_Advantage_Home

http://techsupport.services.ibm.com/guides/contacts.html

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006

http://www.ibm.com/servers/eserver/techsupport.html



Notices

These notices apply to this product.

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:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, 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.

TrademarksThese trademarks apply to this product.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. If these and other IBM trademarkedterms are marked on their first occurrence in this information with a trademark symbol (® or ™), thesesymbols indicate U.S. registered or common law trademarks owned by IBM at the time this informationwas published. Such trademarks may also be registered or common law trademarks in other countries. Acurrent list of IBM trademarks is available on the Web at "Copyright and trademark information" athttp://www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, orboth.

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.


Index

AABEND 0C4 37ABEND 0D6 38ABEND ETE0101

most common reason for seeing 39ABEND U0404 39about this information viiAPF authorization 7

Ccalculating end-to-end response time 5changing the device exclusion list 29CICS

CIHT sessions specifications 33definite response protocol 31releases supported 32SEND exit 34

enabling and disabling the exitusing PLTPI or PLTS 34

enabling and disabling the exitusing transaction KETX 34

table updates required 33CICS definite response protocol

ETE-CICS implementation. 31IBM-provided solution 31installation considerations 32multi-session manager

considerations 32table updates required 33

CICS SEND exit 34CICS transactions

reporting ETE problems 35troubleshooting 38

CIHT parametmerETE EXEC 33sessions specifications 33

CL/Supersession 15, 19coexistence with previous versions 2commands 23

ETE CLRDUMP 23ETE DUMP 23ETE DUMPDXL 24ETE HELP 24ETE NOVERBOSE 24ETE QUIESCE 10, 25ETE RESET 25ETE startup

issuing the ETE command withmultiples instances of ETErunning 13

ETE SYSTEMS 26ETE TRACEOFF 26ETE TRACEON 26ETE USER 26ETE USERS 7, 27, 43syntax 23

creating a device exclusion list 29customer support 50

customizing multi-session managerproduct 11, 15, 19

customizing the ETE startup JCL 7

DDB2 conversion failure 38defining the exclusion list 29definite response protocol 5

CICS 31excluding devices that cannot tolerate

definite response protocol 7definite response requests 29definition 1determining which products are using

ETE services 11device exclusion list

changing 29creating 29defining 29device exclusion list

example 29protecting device from definite

response requests 29rules 29

dumps 35

Eenabling and disabling the CICS SEND

exit using PLTPI or PLTS 34enabling and disabling the CICS SEND

exit using transaction KETX 34end-to-end response time

calculating 5defined 5measuring 5

ETEaddress space abends 39address space not active 41CICS definite response protocol

installation considerations 32multi-session manager

considerations 32table updates required 33

CLRDUMP command 23Coexistence with previous versions 2command arguments 23command syntax 23commands 23

arguments 23configuration tool updates 1creating a device exclusion list 29DD cards do not match 41defined 1, 5DUMP command 23DUMPDXL command 24ESQA storage usage 39ETE-CICS definite response

implementation. 31

ETE (continued)HELP command 24IMS Message OEI971 41installation and configuration

information 3making the subsystem available to the

OMEGAMON XE monitoringagents 7

messages and codes 35multiple load attempts error 40new in this release 1NOVERBOSE command 24operating ETE with multi-session

manager products 15, 19QUIESCE command 25recycling 10recycling a major node 10reporting problems 35requirements 2

OMEGAMON XE monitoringagents on z/OS 2

terminal types supported 2VTAM releases 2

RESET command 25running multiple copies 7, 13

including DDNAME statements toidentify ETE subsystems 13

issuing the ETE command withmultiples instances of ETErunning 13

running on a single system 2running with NetView Performance

Monitor 13starting 7

from the z/OS operator console 9stopping 10SYSTEMS command 26TRACEOFF command 26TRACEON command 26troubleshooting 37USER command 26users 1USERS command 27verifying correct startup 7verifying ETE and OMEGAMON

operation 7ETE CLRDUMP command 23ETE DUMP command 23ETE DUMPDXL command 24ETE EXEC

CIHT parametmer 33ETE HELP command 24ETE NOVERBOSE command 24ETE QUIESCE 25

with automation 25ETE QUIESCE command 10, 25ETE RESET command 25ETE services

determining which products areusing 11

ETE startup 7


ETE startup (continued)excluding devices 7issuing the ETE command with

multiples instances of ETErunning 13

JOB statement TIME parameter 7RKANPARU dataset 7TIME parameter 7

ETE SYSTEMS command 26ETE TRACEOFF command 26ETE TRACEON command 26ETE USER command 26ETE USERS command 27, 43

output 7exception response protocol 5excluding devices that cannot tolerate

definite response protocol 7excluding some devices 29

Ffixes, obtaining 50

Hhost response time 16, 20

IIBM Redbooks 49IBM Support Assistant 49IBM Tivoli Distributed Monitoring and

Application Management Wiki 49IMS Message OEI971 41including DDNAME statements to

identify ETE subsystems 13installation and configuration

information 3ISA 49issuing the ETE command with multiples

instances of ETE running 13

JJCL

startupCICS definite response

parameter 8control option parameter 7customzing 7time parameter 7

Llibraries

OMEGAMON II for MainframeNetworks 45

OMEGAMON XE for MainframeNetworks 45

Mmaking the ETE subystem available to

the OMEGAMON XE monitoringagents 7

message DFHZ3465 38message DSNL500I 38message ETE0090 42message GIM35908I 42message OM8389 42MSM

See multi-session managerproduct, 15, 19

multi-session manager productconsiderations with CICS definite

response protocol 32customizing 11, 15, 19IBM CL/Supersession 15, 19multiple VLUs 15, 19operating ETE with MSMs 15, 19single VLU 15, 19single VLU with multiple real

terminals 15, 19troubleshooting 43

NNetView Performance Monitor

running with ETE 13network response time 16, 20new in this release 1

Oobtaining OMEGAMON debug screens

ETE problems 35OMEGAMON II for MVS

OM8389 42OMEGAMON XE monitoring agents on

z/OSETE installation and configuration

information 3making the subsystem available to

monitoring agents 7prerequisite activities 7supported versions 2

Pproblem resolution 49problems

reporting 35protecting device from definite response

requests 29publications

OMEGAMON II for MainframeNetworks 45

OMEGAMON XE for MainframeNetworks 45

Rrecycling a major node 10recycling ETE 10Redbooks 49reporting ETE problems 35

reporting ETE problems (continued)CICS transaction problems 35dumps 35obtaining OMEGAMON debug

screens 35procedure 35software release and maintenance

levels 35system and network configuration 35traces 35

requirements 2OMEGAMON XE monitoring agents

on z/OS 2terminal types supported 2VTAM releases 2

response timecalculating 5

RKANPARU datasetadding to ETE startup 7

running ETE on a single system 2running multiple copies of ETE 7, 13

Ssense code 200A 38SMP/E

GIM35908I message 42Software Support 49

contacting 50receiving weekly updates 50

starting ETE 7from the z/OS operator console 9success message 7

stopping ETE 7, 10storage usage 39support assistant 49Support Assistant 49

TTIME parameter 7traces 35troubleshooting 37

ABEND 0C4 37ABEND 0D6 38address space not active 41CICS transactions 38DB2 conversion failure 38DD cards to not match 41ESQA storage usage 39ETE address space abends 39IMS Message OEI971 41multiple load attempts 40OMEGAMON II for MVS message

OM8389 42registration failure 40SMP/E message GIM35908I 42startup request failed with

ETE0090 42TSO signon using multi-session

manager product 43TSO 43

Uusers 1


Vverifying ETE and OMEGAMON

operation 7verifying that ETE has started

correctly 7Version 6.2.0

updates 1virtual logical units (VLUs) 15, 19

running with a multiple VLUs 15, 19running with a single VLU 15, 19running with a single VLU with

multiple real terminals 15, 19

Wwiki 49

Index 57

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

OMEGAMON and IBM Tivoli Management Services on z/OSEnd-to-End Response Time Feature ReferenceVersion 6.2.0

Publication No. SC27-2303-02

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-2303-02

SC27-2303-02

��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-2303-02