end-to-end response time reference manual, v500

Reference ManualEnd-to-End Response Time Feature (ETE)

Version 500

GC32-9311-00

August 1999

Candle Corporation201 North Douglas Street

El Segundo, California 90245

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER,AF/REMOTE, Availability Command Center, Candle Command Center, Candle Electronic Customer Support,Candle Logo, Candle Management Server, Candle Management Workstation, Candle Technologies,CL/CONFERENCE, CL/SUPERSESSION, CT, CT/Data Server, CT/DS, DB Logo, DB/QUICKCHANGE,DELTAMON, ETEWatch, IntelliWatch, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e,OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, Solutions for NetworkedBusinesses, and Transplex.

Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS,Amsys, AUTOMATED FACILITIES, Availability Management Systems, Candle Business Partner Logo, CandleDirect Logo, CandleLight, CCC, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW,Command & Control, CommandWatch, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services,CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench,CT/Workstation Server, CT/WS, DB/DASD, DB/EXPLAIN, DB/MIGRATOR, DB/QUICKCOMPARE, DB/SMU,DB/Tools, DB/WORKBENCH, Design Network, DEXAN, eBA*ServiceMonitor, End-to-End, Enterprise CandleCommand Center, Enterprise Candle Management Workstation, EPILOG, ERPNet, ESRA, HostBridge, IntelliWatchPinnacle, Lava Console, Messaging Mastered, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, OMA, OMCGateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER StatusManager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ,PQConfiguration, PQEdit, PQScope, Response Time Network, Roma, Roma Broker, Roma BSP, Roma Connector,Roma Developer, Roma FS/A, Roma FS/Access, Roma Network, Roma Systems Manager, RTA, RTN,SentinalManager, Solutions for Networked Applications, Status Monitor, Tracer, Unified Directory Services andVolcano.

Trademarks and registered trademarks of other companies: AIX, DB2, and MQSeries are registeredtrademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademarkof SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/OpenCompany Ltd. HU-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems,Inc.

All other company and product names used herein are trademarks or registered trademarks of their respectivecompanies.

ProtoView Development Corp. - Contains DataTable Version 3.0 Copyright 1989—1996 by ProtoViewDevelopment Corp. and distributed under license by Candle Corporation.

Copyright 1992 – 1999, Candle Corporation, a California corporation. All rights reserved. International rightssecured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Testsin Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Usingthe XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring,Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment forComputer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility,Patent No. 5,848,234; Communications on a Network, Patent Pending; End-to-End Response Time Measurement forComputer Programs, Patent Pending; Improved Message Queuing Based Network Computing Architecture, PatentPending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by theGovernment is subject to restrictions set forth in the applicable license agreement and/or the applicable governmentrights clause.

This documentation contains confidential, proprietary information of Candle Corporation that is licensed for yourinternal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents

List of Illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Read This First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

| Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11What Is End-to-End Response Time?. . . . . . . . . . . . . . . . . . 11How Does ETE Calculate Response Time?. . . . . . . . . . . . . . 12What Terminals Are Supported?. . . . . . . . . . . . . . . . . . . . . 13Which VTAM Releases Are Supported?. . . . . . . . . . . . . . . . 13How Does ETE Relate to OMEGAMON?. . . . . . . . . . . . . . . 13

| When is Version 500 Required?. . . . . . . . . . . . . . . . . . . . . 13Is ETE a Single System? . . . . . . . . . . . . . . . . . . . . . . . . . . 14

| Can Version 500 Coexist with Prior Releases?. . . . . . . . . . . . 14Can ETE Coexist with Other Software?. . . . . . . . . . . . . . . . 14Where Are the Installation Instructions?. . . . . . . . . . . . . . . . 14

| What's New in Version 500?. . . . . . . . . . . . . . . . . . . . . . . . 15| What About Prior Releases?. . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2. Starting ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Shut Down All OMEGAMONs That Use ETE. . . . . . . . . . . . 17Customize ETE Startup JCL. . . . . . . . . . . . . . . . . . . . . . . . 17Add the RKANPAR Dataset . . . . . . . . . . . . . . . . . . . . . . . . 18Check TIME Parameter on JOB Statement. . . . . . . . . . . . . . 19Important Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Start ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Verify ETE Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Make ETE Available to OMEGAMONs . . . . . . . . . . . . . . . . 21Verify OMEGAMON and ETE Operation . . . . . . . . . . . . . . . 21Multi-Session Manager (MSM) Customization. . . . . . . . . . . . 21Stopping ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Major Node Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22ETE Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Chapter 3. Running Multiple Copies of ETE . . . . . . . . . . . . . . . 23DDNAME Identifying ETE Subsystems . . . . . . . . . . . . . . . . 23Issuing ETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Running ETE with IBM's NPM . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 4. Multi-Session Manager Interface . . . . . . . . . . . . . . . 25MSM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Operating ETE with MSMs . . . . . . . . . . . . . . . . . . . . . . . . 27

Contents 3

Chapter 5. ETE Command . . . . . . . . . . . . . . . . . . . . . . . . . . .29ETE Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29ETE Command and Arguments. . . . . . . . . . . . . . . . . . . . . . 29

Chapter 6. Device Exclusion List . . . . . . . . . . . . . . . . . . . . . . . 35Protecting Devices from DR . . . . . . . . . . . . . . . . . . . . . . . . 35Defining the Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . 35Exclusion List Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Changing the Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 7. CICS Definite Response . . . . . . . . . . . . . . . . . . . . . 37Solution Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Graphic Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

| CICS Releases Supported. . . . . . . . . . . . . . . . . . . . . . . . . . 38MSM Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 39CICS Table Updates Required. . . . . . . . . . . . . . . . . . . . . . . 39ETE EXEC Parameter CIHT. . . . . . . . . . . . . . . . . . . . . . . . 40CICS SEND Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Enabling/Disabling Exit by PLTPI/PLTSD . . . . . . . . . . . . . . 41Enabling/Disabling Exit by Transaction KETX. . . . . . . . . . . . 42

Chapter 8. Problem Reporting . . . . . . . . . . . . . . . . . . . . . . . . .43

Appendix A. Messages and Codes . . . . . . . . . . . . . . . . . . . . . 47| Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Sense Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Appendix B. Candle Customer Support . . . . . . . . . . . . . . . . . . 73

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

4 End-to-End Reference Manual Version 500

List of Illustrations

1. Calculating Response Time. . . . . . . . . . . . . . . . . . . . . . . . . . 122. ETE USERS Command Output . . . . . . . . . . . . . . . . . . . . . . . 203. MSM Configuration, Real Terminal Using a Single VLU. . . . . . 254. MSM Configuration, Real Terminal Using Multiple VLUs . . . . . 265. MSM Configuration, Multiple Real Terminals Using Single VLU. 266. Sample RKANPAR PDS Member KETXDLDR . . . . . . . . . . . . 367. ETE DR Implementation for CICS . . . . . . . . . . . . . . . . . . . . . 38

List of Tables

1. CIHT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402. Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

List of Illustrations 5

Read This First

Preface

About this document

This manual is intended for those who are responsible for operating theEnd-to-End Response Time Feature (ETE) and includes:

Á a description of ETE

Á an explanation of how to start ETE after installation and customizationhave been completed

Á a description of each ETE command argument

Á a description of the ETE error messages, return codes, and sense codes

The ETE procedure is installed into your procedure library during CandleInstallation/Customization Assistance Tool (CICAT) configuration. TheConfiguration and Customization Guidefor each OMEGAMON thatincorporates ETE describes the CICAT configuration process.

For information on using ETE to monitor response time within a particularOMEGAMON, refer to the appropriate OMEGAMON documentation.

For information about the enhancements to ETE that Version 500 provides,see “What's New in Version 500?” on page 15.

Read This First 7

Adobe Portable Document Format

Introduction

Candle supplies documentation in the Adobe Portable Document Format(PDF). The Adobe Acrobat Reader prints PDF documents with the fonts,formatting, and graphics in the original document. To print a Candledocument, do the following:

1. Specify the print options for your system. From the Acrobat ReaderMenu bar, select File > Print Setup... and make your selections. Asetting of 300 dpi is highly recommended as is duplex printing if yourprinter supports it.

2. To start printing, select File > Print on the Acrobat Reader Menu bar.

3. On the Print popup, select one of the Print Range options for

Á a single pageÁ a range of pagesÁ all of the document

4. (Optional) To fit oversize pages to the paper size currently loaded onyour printer, select the Shrink to Fit option.

Printing problems?

Your printer ultimately determines the print quality of your output.Sometimes printing problems can occur. If you experience printingproblems, potential areas to check are:

Á settings for your printer and printer driver. (The dpi settings for bothyour driver and printer should be the same. A setting of 300 dpi isrecommended.)

Á the printer driver you are using. (You may need a different printer driveror the Universal Printer driver from Adobe. This free printer driver isavailable at www.adobe.com.)

Á the halftone/graphics color adjustment for printing color on black andwhite printers. (Check the printer properties underStart > Settings >Printer. For more information, see the online help for the AcrobatReader.)

Á the amount of available memory in your printer. (Insufficient memorycan cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentationfor your printer or contact your printer manufacturer.


Documentation Conventions

Introduction

Candle documentation adheres to accepted typographical conventions forcommand syntax. Conventions specific to Candle documentation arediscussed in the following sections.

Panels and figures

The panels and figures in this document are representations. Actual productpanels may differ.

Revision bars

Revision bars (|) may appear in the left margin to identify new or updatedmaterial.

Variables and literals

In examples of command syntax, uppercase letters are actual values (literals)that the user should type; lowercase letters are used for variables thatrepresent data supplied by the user. Default values are underscored.

LOGON APPLID(cccccccc)

In the above example, you type LOGON APPLID followed by an applicationidentifier (represented bycccccccc) within parentheses. The number ofcharacters indicates the maximum allowable length of the variable.

Note: In ordinary text, variable names appear in italics.

Read This First 9

Symbols

The following symbols may appear in command syntax.

Symbol Usage

| The 'or' symbol is used to denote a choice. Eitherthe argument on the left or the argument on the rightmay be used. Example:

YES | NO

In this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments notenclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]

In this example, DEST is a required argument andALTDEST is optional.

{ } Some documents use braces to denote requiredarguments, or to group arguments for clarity.Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORTkeyword must be specified with a value ofSUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile -[COMPRESS={YES | NO}]

In this example, the COMPRESS keyword isoptional. If specified, the only valid values are YESor NO. If omitted, the default is YES.

␣ The symbol ␣ indicates a blank space, when neededfor clarity.


| Chapter 1.| Introduction

This chapter describes the End-to-End Response Time Feature (ETE), how itcalculates response time, and what terminals are supported.

What Is End-to-End Response Time?

End-to-end response time is the elapsed time between the moment that a userpresses a key (Enter, F1 through F24, PA1, PA2, PA3, or Clear) and themoment that a response is received at the terminal. For example, if you starta stopwatch when a user presses Enter and stop it when the terminal receivesthe application's first response to the user's request, the stopwatch shows theend-to-end response time for that request.

To measure end-to-end response time, ETE places itself inside one of theVTAM SNA layers. In this location ETE can time all SNA traffic that flowsthrough VTAM.

End-to-end response time measurement requires that VTAM internal tracewith the PIU option is active. This is started automatically when ETE isactivated.

ETE captures end-to-end response time for applications that use either thedefinite response protocol or the exception response protocol.

Definite Response Protocol

Under the definite responseprotocol, the application asks the terminalcontroller to respond to transmitted data by indicating whether or not thetransmission was successful. The application must then wait for thecontroller's response before continuing. Because the controller responds toall transmissions, end-to-end response time is relatively easy to monitor underthe definite response protocol.

Chapter 1. Introduction 11

Exception Response Protocol

Under the exception responseprotocol, the application asks the controller torespond only if an error occurs during data transmission to the terminal.Because ETE can measure end-to-end response time only for transactions thatrequire a response from the controller, ETE must turn on definite responsefor applications that use the exception response protocol. After it measuresthe response time, ETE discards the definite response before it flows to theapplication. As a result, the application never receives the definite responseand is not even aware that a definite response was elicited.

How Does ETE Calculate Response Time?

ETE measures the time between SNA events from inside VTAM. Themeasured time begins when the request flows through VTAM toward theapplication; it ends when VTAM receives the definite response from theterminal controller. There is only one portion of end-to-end response timethat ETE cannot capture directly and must estimate—the time before theuser's request reaches VTAM (T1 minus T0) in the figure below).

End-to-end response timeHost response timeNetwork response time

= (T6 - T1)= (T4 - T1)= (T6 - T4)

Host

ResponseTime

Monitor

VTAM Application

Controller

request

NCP

T6T5

+RSP

T4 T3

T2T1T0

Figure 1. Calculating Response Time

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 definiteresponse to flow from the controller to VTAM (T6 minus T5). This is truebecause all definite responses and most inbound requests contain little data.Therefore, ETE calculates end-to-end response time as (T6 minus T1).


What Terminals Are Supported?

ETE Version 500 provides response time data for the following real LUtypes:

Á SNA LU type 1Á SNA LU type 2Á SNA LU type 3

Which VTAM Releases Are Supported?

ETE Version 500 supports VTAM 3.4 and above.

How Does ETE Relate to OMEGAMON?

ETE provides a service to OMEGAMON. ETE measures the host andnetwork components of response time and furnishes them to anyOMEGAMON that displays response time. Currently, the OMEGAMONproducts that obtain response time from ETE are:

Á OMEGAMON II for CICSÁ OMEGAMON II for IMSÁ OMEGAMON II for MVSÁ OMEGAMON II for VTAM

| When is Version 500 Required?

| Use Version 500 as the ETE version for

| Á OMEGAMON II for CICS, Versions 400 and above.| Á OMEGAMON II for IMS, Versions 400 and above.| Á OMEGAMON II for MVS, Versions 400 and above.| Á OMEGAMON II for VTAM, Versions 400 and above.

| ETE Version 150 is required only if you are running a pre-Version 400| OMEGAMON.


Is ETE a Single System?

For all of the Candle products that use ETE Version 500 for response time,only one ETE Version 500 system is required, regardless of the number ofCandle products you are running.

| Can Version 500 Coexist with Prior Releases?

| ETE Version 500 running in one address space can coexist with a previous| version of ETE running in another address space.

| The only time you are required to run two ETE systems is when you are| running some OMEGAMONs that require Version 500 and other| OMEGAMONs that require an ETE release prior to 160 (pre-V400| OMEGAMONs).

| You can run multiple ETE systems for testing, but for production we| recommend using the minimum number of ETE systems required. For more| information about running multiple ETE systems, see “Running Multiple| Copies of ETE” on page 23.

Can ETE Coexist with Other Software?

ETE can coexist with the following software from other vendors:

Á NetSpyÁ Netview Performance MonitorÁ CA-MAZDAMONÁ Vital Signs for VTAM

Where Are the Installation Instructions?

For each OMEGAMON that uses ETE, the ETE proc is installed into yourproclib during the CICAT configuration process. We recommend that yourOMEGAMONs share the same ETE started task. For CICAT information,see the OMEGAMON'sConfiguration and Customization Guide.

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


| What's New in Version 500?

| The enhancements to ETE provided by Version 500 are solely internal.

| What About Prior Releases?

| ETE Version 150 is required for pre-Version 400 OMEGAMONs.

| Versions of ETE prior to 150 are no longer supported.


Chapter 2. Starting ETE

This chapter explains how to start ETE after it is installed and customized asdescribed in your OMEGAMON installation documentation.

For information on using ETE within your OMEGAMON product, refer tothe response time section of your OMEGAMON documentation.

To start ETE, follow the steps below in order.

Shut Down All OMEGAMONs That Use ETE

To shut down OMEGAMONs that use ETE:

1. Refer to the appropriate OMEGAMON manual for an explanation of itsstop procedure.

2. Issue an ETE QUIESCE command to stop ETE. (See ETE QUIESCEcommand on page 31 for details.)

Customize ETE Startup JCL

The ETE startup JCL is named CANSET. Control the monitoring of LUtype 1 and 3 devices with a parameter on the EXEC statement.

This is the format for the EXEC statement:

EXEC PGM=KETESTRN[,PARM='pppppp[,CIHT=nnnnn]']

where the variables are:

pppppp Control option parameter:

NFDRNL2 Monitor, but do not force DR on LU type 1 and3 devices (default).

This option allows collection of byte countinformation but not response time data for LUtype 1 and 3 devices (unless session is usingDR of its own accord).

Chapter 2. Starting ETE 17

FDRNL2 Monitor and force DR on LU type 1 and 3devices.

This option allows collection of byte countinformation and response time data for LU type1 and 3 devices.

Do not use this option with 3816 or 3820printers.

FAILNL2 Fail monitor requests for LU type 1 and 3devices.

This option prevents collection of both bytecount information and response time data forLU type 1 and 3 devices.

nnnnn CIHT table size for CICS definite response. (See “CICSDefinite Response” on page 37)

Add the RKANPAR Dataset

To enable or disable other control options for the ETE address space, add theRKANPAR dataset to the ETE startup JCL. See “Device Exclusion List” onpage 35.

Add the following statement directly after the EXEC PGM=KETESTRNstatement:

//RKANPAR DD DSN=hilev.RKANPAR,DISP=SHR

The RKANPAR dataset is where you specify information about enabling anddisabling control options.

If you do not add the RKANPAR dataset to the ETE startup JCL, noadditional startup options (other than those on the EXEC statement) areprocessed.

Device Exclusion List

To exclude devices that cannot tolerate definite response protocol from ETEmonitoring:

1. Create member KETXDLDR in the RKANPAR library.

2. In member KETXDLDR, list the devices to exclude. You can refer tomember KETXDLDR in the TKANSAM dataset which contains asample device exclusion list.


3. Make sure that ddname RKANPAR is included in the ETE JCL.

See “Device Exclusion List” on page 35 for more information aboutexcluding LU names from ETE monitoring.

Check TIME Parameter on JOB Statement

The sample ETE started task JCL is shipped without a TIME parameter onthe JOB statement. Many sites maintain a default TIME parameter value(such as 1439 or 1440) that prevents started tasks from timing out. If yoursite's default TIME parameter value allows timeout, be sure to add anappropriate TIME parameter to the ETE JOB statement. The ETE startedtask must not timeout.

Important Prerequisites

These are important prerequisites to starting ETE:

1. Plan on running only one ETE, regardless of the number ofOMEGAMONs or sessions using ETE.

2. Make sure that VTAM is active.

3. Because ETE must be active before OMEGAMON can use it,. plan tostart ETE as soon as possible after VTAM initializes. If any sessionswere started before ETE startup, those terminals' binding information areunavailable to ETE. This limits ETE's effectiveness for those terminals.

4. ETE requires the VTAM internal trace to be running. Normally ETEstarts the trace automatically.

If you run CA-MAZDAMON on the same system with ETE, you mustmanually start the VTAM Internal Trace with the PIU option.Alternatively, you can specify that the trace start at VTAM startupthrough the VTAM start list parameter (ATCSTRxx). See the IBMVTAM Installation and Resource Definitionmanual for specification ofthe TRACE start list parameter.

5. Make sure the STEPLIB DD statement in your OMEGAMON productJCL procedure points to the Candle product runtime load library,RKANMOD and is APF-authorized.

6. If you want to run concurrent versions of ETE, read “Running MultipleCopies of ETE” on page 23 before starting ETE.


Start ETE

To start ETE, issue this command at the MVS operator console:

S CANSET

where CANSET is the name of the ETE address space JCL procedure.

Result: The ETE Version 500 address space remains active until it isquiesced.

To verify that ETE started successfully, look for this message on the operatorconsole:

ETEðð91 ETE VERSION 5ðð SUCCESSFULLY INITIALIZED

Verify ETE Start

At an MVS console, enter the ETE USERS command to verify that ETEstarted. Check the command output which will appear as shown below.

à ðETE USERS

ETEððð2: ETE V5ðð #ðð LOAD DSN=hilev.RKANMOD

ETEðð4ð: JOBNAME ASID TCB TYPE

ETEðð41: USERðð1 ðð176 ðð7BE458 RSPTIME

ETEðð41: ETE5ðð ðð175 ðð7EDB8ð CAPTURE

ETEðð41: ETE5ðð ðð175 ðð7EF1F8 CAPTURE


ETEððð3: COMPLETE

á ñ

Figure 2. ETE USERS Command Output

The first line of console output shows

Á ETE version number

Á subsystem identifier (00 is the default)

Á load library from which you installed ETE.

The ETE started task name appears in the display several times because ETEis a user of its own internal services.


Make ETE Available to OMEGAMONs

To make ETE available to OMEGAMONs, you must set up all of yourOMEGAMONs to load ETE modules from thehilev.RKANMOD library.hilev was defined during OMEGAMON installation, as described in yourOMEGAMON installation documentation.

1. Ensure that the Candle product load library, RKANMOD is included in aSTEPLIB DD statement for each of your OMEGAMON jobs and startedtasks. This library contains OMEGAMON and ETE load modules.

2. Ensure that all libraries in the STEPLIB concatenation areAPF-authorized.

Verify OMEGAMON and ETE Operation

1. Start each OMEGAMON that uses ETE.

2. Verify ETE operation by starting response time monitoring for eachOMEGAMON.

Multi-Session Manager (MSM) Customization

To obtain response time for sessions controlled by an MSM, you mustconfigure the MSM to produce the session switch message. For moreinformation, see “Multi-Session Manager Interface” on page 25.

Stopping ETE

We recommend that you keep ETE running continuously to collect sessioninformation history. If you decide to stop ETE for any reason, issue the ETEQUIESCE command as described on page 31.


Major Node Recycling

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

OMEGAMON II for MVS and OMEGAMON II for VTAM are not affectedby the recycle and do not need to re-establish linkage.

ETE Recycling

We recommend that you keep ETE running for the life of the IPL. However,if you take down ETE, you may notice that some storage is left in the CSA.Do not delete this data because it is reaccessed by ETE when it is restarted.


Chapter 3.Running Multiple Copies of ETE

Under normal conditions, running multiple OMEGAMONs requires only onecopy of ETE.

During test, product migration, or under special circumstances, you may needto start several copies of ETE Version 500, or Version 500 and priorreleases. This chapter describes considerations for running multiple copies ofETE. You can run

Á multiple copies of ETE Version 500Á multiple copies of a prior ETE releaseÁ ETE Version 500 and a prior ETE release

DDNAME Identifying ETE Subsystems

When using multiple copies, to identify and run a specific copy of ETE 500you must:

Á Include this DD statement in each ETE JCL stream:

//RKETVTnn DD DUMMY

where nn is a unique numeric suffix between 00 and 15, identifying thesubsystem.

Á For ETE releases prior to 500, use this DD statement to identify and runa specific copy of ETE:

//RSPVTMnn DD DUMMY

where nn is a unique numeric suffix between 00 and 15, identifying thesubsystem.

Á A maximum of four ETE address spaces can run concurrently in a singledomain.

Important: To identify the ETE subsystem to the OMEGAMON using it, besure to also include the DD DUMMY statement, as described above, in theOMEGAMON JCL stream.

Chapter 3. Running Multiple Copies of ETE 23

Issuing ETE Command

If you are running multiple copies of ETE, be sure to direct ETE commandsto the proper ETE using the following syntax:

ETE[nnn] cccccccc

nnn Three-digit ETE version number or two-digit subsystemidentifier.

cccccccc ETE command name.

To direct ETE commands to the proper ETE when more than one ETEsystem is running, include the version number.

For example, to QUIESCE ETE Version 150, issue this command:

ETE15ð QUIESCE

Running ETE with IBM's NPM

These are special operational considerations when running concurrent ETEsand IBM's Network Performance Monitor (NPM).

Á ETE can coexist with NPM. When NPM starts, it disregards anyexisting interface participant and installs itself as the only front-endinterface to VTAM. This disables ETE operation. ETE detects thiscondition and reinstalls itself in conjunction with NPM.

Á When NPM terminates, it removes itself as an interface participant butdoes not ensure the integrity of other interface participants. ETE alsodetects this condition and recovers from it.

Á If NPM starts or stops when more than one ETE system is running, onlyone ETE recovers. The ETE that recovers depends on various factors atthe time the event occurs. The ETE that does not recover does notimpact the system, but does not report response time information.

Note: We recommend that you do not run multiple copies of ETE withNPM in your production environment because of the limitations statedabove.


Chapter 4.Multi-Session Manager Interface

This chapter describes how ETE interacts with multi-sessionmanagers (MSMs).

MSM Overview

In a configuration with an MSM, such as CL/SUPERSESSION, a terminaluser logs onto the MSM using a real terminal. Then, using a pool of VirtualLogical Unit (VLU) names, the MSM establishes sessions on behalf of thatreal terminal.

Depending on the MSM implementation, you can use the following VLUconfigurations to support multiple logical unit-logical unit (LU-LU) sessions:

Á The MSM establishes multiple sessions on behalf of a real terminal usinga single VLU.

Multi─Session Manager ┌───────────────────────────┐ │ │ │ │┌────────┐ │ ┌──────────┐ │ ┌────────┐│ │ │ │ │ │ │ ││ CICSA │<────────────────>│ VTERM1 │ │<──────>│ TERMA ││ │ │ │ │ │ │ │└────────┘ │ ┌─────>└──────────┘ │ └────────┘ │ │ │┌────────┐ │ │ V i r t u a l ││ │ │ │ ││ TSOA ├<──────────┘ L U ││ │ │ │└────────┘ │ P o o l │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └───────────────────────────┘

Figure 3. MSM Configuration, Real Terminal Using a Single VLU

Chapter 4. Multi-Session Manager Interface 25

Á The MSM establishes multiple sessions on behalf of a real terminal usingmultiple VLUs.

Multi─Session Manager ┌───────────────────────────┐ │ │ │ ┌──────────┐ │┌────────┐ │ │ │ ││ │ │ │ VTERM1 │ ││ CICSA ├<──────────────>│ │ ││ │ │ └──────────┘ │ ┌────────┐└────────┘ │ │ │ │ │ ├<──────>┤ TERMA │┌────────┐ │ │ │ ││ │ │ ┌──────────┐ │ └────────┘│ CICSB ├<──────────────>│ │ ││ │ │ │ VTERM2 │ │└────────┘ │ │ │ │ │ └──────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └───────────────────────────┘

Figure 4. MSM Configuration, Real Terminal Using Multiple VLUs

Á The MSM establishes multiple sessions on behalf ofmultiple realterminals using a single VLU.

Multi─Session Manager ┌───────────────────────────┐ │ │ │ │┌────────┐ │ ││ │ │ ││ CICSA ├<─────────────┐ ││ │ │ │ │ ┌────────┐└────────┘ │ │ │ │ │ │ │ ├<──────>┤ TERMA │┌────────┐ │ │ V i r t u a l │ │ ││ │ │ │ │ └────────┘│ CICSB ├<──┐ │ │ L U ││ │ │ │ │ │ ┌────────┐└────────┘ │ │ │ P o o l │ │ │ │ │ │ ├<──────>┤ TERMB │┌────────┐ └────────┐ │ ┌──────────┐ │ │ ││ │ │ │ └─>│ │ │ └────────┘│ TSO ├<─────────┐ └───>│ VTERM1 │ ││ │ │└─────>│ │ │└────────┘ │ └──────────┘ │ │ │ │ │ └───────────────────────────┘

Figure 5. MSM Configuration, Multiple Real Terminals Using Single VLU


In each configuration above, ETE Version 500 measures the host andnetwork components of response time.

Host response time The time it takes for the data to flow betweenthe application (CICSA, CICSB, TSO) and theVLU.

Network response time The time it takes for the data to flow betweenthe MSM and the real terminal (TERMA,TERMB).

Operating ETE with MSMs

The following conventions apply to ETE operation with MSMs:

Á Both ETE and the MSM must reside in the same VTAM domain.

Á When using ETE through OMEGAMON II for VTAM, the actual PLUof the virtual session (CICS, IMS, TSO,...) can be the same domain,cross domain, or even cross-network.

Á ETE supports MSMs that use the virtual session switching conventionproposed by Computer Associates International. MSMs that follow thisconvention produce a nondisplay 3270 data stream message that is sentto the physical terminal each time a session switch is performed. This isthe session switch message. Many MSMs, including Candle'sCL/SUPERSESSION, support this convention.

To configure CL/SUPERSESSION to produce the session switchmessage, refer to information on the NetSpy recommended installationprocedure in theCL/SUPERSESSION and CL/GATEWAY CustomizationGuide (Version 146 or above).

Á You must start ETE prior to any MSM containing VLUs that ETE willmonitor. ETE does not monitor MSM sessions if it is unaware of theVLU and real terminal relationship. If you cancel or stop the ETEaddress space, response time numbers are not accurate or subsequentattempts to monitor terminals fail until the next restart of the MSM.

Chapter 4. Multi-Session Manager Interface 27

Chapter 5. ETE Command

This chapter describes the ETE operator command. The command syntax isdefined, all command arguments are listed alphabetically with a briefdescription of their function, and the resulting console output is illustrated.

ETE Command Syntax

Issue the ETE operator console command using the following syntax:

ETE[nnn] cccccccc

nnn Three-digit ETE version number (such as 500 or 150) ortwo-digit ETE subsystem identifier (a unique number between00 and 15). This suffix is only required when running multiplecopies of ETE. For more information, see “Running MultipleCopies of ETE” on page 23.

cccccccc ETE command argument

ETE Command and Arguments

ETE accepts the ETE operator console command with an argument. TheETE command with each of its valid arguments is shown below.

ETE CLRDUMP Resets the flag that indicates dumps have beencompleted. This allows additional dump collection.

à ðETE CLRDUMP

ETEððð2: ETE V5ðð #ðð LOAD DSN=hilev.TKANMOD


á ñ

Chapter 5. ETE Command 29

ETE DUMP Creates an SVC dump tailored for ETE problemanalysis and troubleshooting.

à ðETE DUMP

ETEððð2: ETE V5ðð #ðð LOADLIB=hilev.TKANMOD

ETEðð1ð: CANDLE SCHEDULED CSA DUMP IN PROGRESS

ETEðð11: CANDLE SCHEDULED CSA DUMP COMPLETE


á ñ

ETE DUMPDXL Displays the excluded devices.

à ðETE DUMPDXL


ETEð2ð9: DXLHTE=ð14A7ðA8 SLUNAME=DUMMYA

ETEð2ð9: DXLHTE=ð14A798ð SLUNAME=DUMMYB


á ñ

ETE HELP Displays available ETE subsystem commandarguments.

à ðETE HELP


ETEðð7ð: THE FOLLOWING ETE COMMANDS ARE AVAILABLE:

ETEðð71: CLRDUMP -- RESET DUMP FLAG/ALLOW NEW DUMP

ETEðð71: DUMP -- PRODUCE A DIAGNOSTIC ETE SVC DUMP

ETEðð71: DUMPDXL -- LIST EXCLUDED DEVICES

ETEðð71: HELP -- PRODUCE THIS DISPLAY

ETEðð71: QUIESCE -- TERMINATE THE ETE SUBSYSTEM

ETEðð71: RESET -- RESET ETE SUBSYSTEM AND QUIESCE

ETEðð71: SYSTEMS -- DISPLAY ETE SUBSYSTEM INSTALLED

ETEðð71: TRACEON -- START ETE DIAGNOSTIC TRACE

ETEðð71: TRACEOFF -- STOP ETE DIAGNOSTIC TRACE

ETEðð71: USER= -- DISPLAY LUNAMES MONITORED BY A SPECIFIC PRODUCT

ETEðð71: USERS -- DISPLAY PRODUCTS USING THE ETE SUBSYSTEM

ETEðð71: VERBOSE -- PRODUCE A DIAGNOSTIC WTO FOR SELECTED EVENTS

ETEðð71: NOVERBOSE -- CANCEL EFFECTS OF VERBOSE COMMAND


á ñ

ETE NOVERBOSE Cancels the effect of the ETE VERBOSE command.VERBOSE MODE OFF is the default status.

à ðETE NOVERBOSE


ETEðð16: VERBOSE MODE OFF


á ñ


ETE QUIESCE Shuts down ETE. Use this command before applyingmaintenance and restarting ETE. After ETE shutsdown, OMEGAMON receives a return code or sensecode indicating that ETE is not operational. QUIESCEdoes not impact other network monitoring systems.

Stopping the ETE address space using the MVS STOPcommand automatically generates an ETE QUIESCEcommand.

Caution: A small amount of common storage isintentionally left behind and is re-used when ETE isrestarted. Do not free this storage with the CSAAnalyzer because this is not orphan storage.

Note: Stop ETE only when necessary. We recommendthat you start ETE immediately after VTAM startupand that you keep ETE running continuously to collectsession information history.

à ðETE QUIESCE


ETEðð51: QUIESCE COMPLETE


á ñ

ETE RESET Use this command only at the direction of CandleCustomer Support.

Resets VTAM interfaces and quiesces ETE subsystemand address space. ETE RESET impactsOMEGAMON and other network monitoring systems.

Caution: Use this command only at the direction ofCandle Customer Support.

à ðETE RESET


ETEðð72: SSTB SUBSYSTEM RESET SUCCESSFUL

ETEðð73: VTAM INTERFACE RESTORED


á ñ


ETE SYSTEMS Displays ETE subsystem status.

à ðETE SYSTEMS


ETEðð3ð: VERSION ## CMD PREF STATUS INST TYPE

ETEðð31: V5ðð ðð ETE5ðððð ACTIVE STATIC


á ñ

ETE TRACEOFF Stops ETE problem determination diagnostic trace.Trace off is the default status.

à ðETE TRACEOFF


ETEðð79: ETE DIAGNOSTIC TRACE STOPPED


á ñ

ETE TRACEON Starts ETE problem determination diagnostic trace.

à ðETE TRACEON


ETEðð78: ETE DIAGNOSTIC TRACE STARTED


á ñ

ETE USER=userid Displays all LU names being monitored by the specificproduct using ETE.userid is a job name as shown inthe ETE USERS command display.

à ðETE USER=USERðð1


ETEðð4ð: USERðð1 : ASCB=ððEE9ð8ð, TCB=ðð7C5458

ETEðð44: Lðð2145ð/TSOGðð21 Lðð2774ð/SMVTAMG Lðð2799ð/RGSSðð1N

ETEðð44: L613A45 /V146GTW1 L613A74 /OIVTAMGð L6151ð8 /SUPGATEG

ETEðð44: L615A1ð6/V146GTW1 L635 /TSOGðð28


á ñ


ETE USERS Shows the STCNAME or JES JOBNAME, ASID, andTCB address of each product using ETE.

à ðETE USERS


ETEðð4ð: JOBNAME ASID TCB TYPE

ETEðð41: USERðð1 ðð176 ðð7BE458 RSPTIME




á ñ


Chapter 6.Device Exclusion List

This chapter describes a feature of ETE you can use to exclude devices fromETE monitoring, even though they have been defined for monitoring by oneor several OMEGAMON products. This exclusion takes effect whetherOMEGAMON defined specific or generic SLU devices for monitoring.

Protecting Devices from DR

Although you use ETE to monitor response time for VTAM applications insession with SLU devices, you can exclude SLU devices that are not tolerantof the definite response (DR) requests issued by ETE.

To do this, set up a device exclusion list specifying those SLUs that youwant to exclude from DR requests. The SLUs in the list are defined in theETE component address space and are protected from DR requests.

Defining the Exclusion List

To create an exclusion list, you must create an KETXDLDR member in theRKANPAR dataset. You can refer to the sample KETXDLDR member inthe TKANSAM dataset.

Use the following syntax to define the exclusion list:

Card columns 1-71 Free-form positional 1- to 8-byte LU names separatedby blanks or commas. Do not mix comments withpositional operands.

Note: An asterisk (*) in column 1 indicates a commentline, all information on that line is ignored.

See “Add the RKANPAR Dataset” on page 18 for information aboutRKANPAR in the ETE JCL.

Chapter 6. Device Exclusion List 35

Exclusion List Example

The following example shows how KETXDLDR excludes SLUs frommonitoring by ETE.

************************************************************************ððð1ðððð

* MEMBER: KETXDLDR *ððð2ðððð

* *ððð3ðððð

* FUNCTION: SAMPLE DR DEVICE EXCLUSION LIST *ððð4ðððð

* *ððð5ðððð

************************************************************************ððð7ðððð

DEVICEð1 ððð8ðððð

DEVICEð2 DEVICEð3 ððð81ðð1

DEVICEð4,DEVICEð5 ððð813ð1

Figure 6. Sample RKANPAR PDS Member KETXDLDR

Rules:

1. You can code more than one device on one line, separated by commas orblanks.

2. Wildcards, masks, and generic device names are not supported.

Changing the Exclusion List

You can change the device exclusion list in the KETXDLDR member of theRKANPAR dataset at any time.

To implement the changes, you must recycle (stop and then restart) ETE.


Chapter 7.CICS Definite Response

This chapter describes a feature of ETE Version 500 that prevents immediateresponse mode protocol violations during CICS sessions.

To monitor response time, ETE may change an exception response to adefinite response (DR). If this response is immediately followed by anotherPIU with DR requested, the CICS session may experience an immediateresponse mode protocol violation (sense code X'200A'). By providing aCICS SEND exit, this feature ensures that the first request is answered beforethe second request is sent, thus preventing CICS session termination(DFH3465).

The Candle-supplied CICS SEND exit forces DR only when all of thefollowing are true:

Á There is a last-in-chain or only-in-chain PIU.Á End-of-bracket or change-direction is in effect.Á The BIND image allows for DR and specifies FM profile 3.Á The session is monitored by ETE running on the same host system as

CICS.

Solution Provided

For this feature, Candle supplies the following:

1. module KETXCOUN for the standard CICS SEND exit XZCOUT

2. enabling and disabling of the CICS SEND exit in two forms:

a. PLTPI/PLTSD module KETXCPLN to enable the exit at CICSstartup and disable the exit at CICS shutdown

b. CICS transaction KETX to directly enable or disable the exit

3. new parameter CIHT on the ETE EXEC statement to specify the CIHTtable size

Chapter 7. CICS Definite Response 37

Graphic Overview

The following diagram illustrates ETE's CICS DR implementation.

┌─────────┐ │ │ CICS initialization │ │ CICS termination ┌────────────┐ │ │ CICS transaction KETX │ ├───5 Enable exit│ ├────────────────────────5│ KETXCPLN │ │ │ │ ├───5 Disable exit│ C │ └────────────┘ │ │ │ ││ I │ CICS Send Exits ┌──────────┐ │ │ │ │ │ │ ┌──────────────────┐ │ ││ C │ │ │ │ │ │ │ │ other exits │ │ │ │ │ │ │ │ ││ S │ ┌─┴────────────────┐ │ │ │ │ │ SEND │ ├─┘ │V T A M│ to │ ├─────5│ ETE's ├────────5│ ├────5terminal│ │ │ KETXCOUN │ │ │ │ │ │ │ │ │ │ │ └──────────────────┘ │ │ └─────────┘ & │ │ │ │ │ │ │ │ │ └──────────┘ │ │ │ 6 ┌───────────────────────┐ │ │ │ │

│ E T E │ │ │ │ │ └───────────────────────┘

Figure 7. ETE DR Implementation for CICS

| CICS Releases Supported

| Because this feature uses a CICS exit, ETE is now CICS release sensitive.| The following CICS releases are currently supported:

| Á 2.1.2| Á 3.1.1| Á 3.2.1| Á 3.3.0| Á 4.1.0| Á TS 1.1| Á TS 1.2| Á TS 1.3


MSM Considerations

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

Installation Considerations

You must include the Candle product load library, RKANMOD, in STEPLIBand DFHRPL concatenations in the CICS startup JCL. This library includesETE as well as OMEGAMON modules.

You can find the parameter CIHT on the ETE EXEC statement. You maychoose not to enable this featurement by specifyingCIHT=ð. For moreinformation on the CIHT parameter, see “ETE EXEC Parameter CIHT” onpage 40 and “Customize ETE Startup JCL” on page 17.

CICS Table Updates Required

To initialize ETE support components in the CICS address space, you mustmodify CICS control tables as follows:

1. For CICS 2.1.2, update the SIT to include

EXITS=YES EXEC=YES

2. For automatic enabling/disabling of the CICS SEND exit, update the PLTto include the following statement in the second stage of initialization inthe PLTPI list and in the first stage of shutdown in the PLTSD list:

DFHPLT TYPE=ENTRY,PROGRAM=KETXCPLN

3. For manual enabling/disabling of the exit via transaction KETX, define anew transaction and two new programs in one of two ways:

a. If you manually edit PCT and PPT tables, do the following:

1) Update the PCT to include

DFHPCT TYPE=ENTRY,TRANSID=KETX,PROGRAM=KETXCPLN, X TRNPRTY=255,TWASIZE=ð,DTB=NO, X TPURGE=YES,SPURGE=NO,SCRNSZE=ALTERNATE

2) Update the PPT to include


DFHPPT TYPE=ENTRY,PROGRAM=KETXCPLN,PGMLANG=ASSEMBLER DFHPPT TYPE=ENTRY,PROGRAM=KETXCOUN,PGMLANG=ASSEMBLER

b. If you use transaction CEDA to define resources online, do thefollowing:

1) For CICS 3.1.1, make sure that group DFHEXEC is installed.

2) Define transaction KETX with the same attributes specified bythe PCT entry in item 3.a.1 above.

For CICS 3.3.0 and above, specify TASKDATAKEY=CICS.

If you migrate resource definitions from a prior CICS release,make sure that TASKDATAKEY=CICS.

3) Define programs KETXCPLN and KETXCOUN with the sameattributes specified by the PPT entries in item 3.a.2 above.

For CICS 3.3.0 and above, specify EXECKEY=CICS.

If you migrate resource definitions from a prior CICS release,make sure that EXECKEY=CICS.

ETE EXEC Parameter CIHT

CIHT is the parameter on the ETE EXEC statement you use to specify thenumber of entries in the ETE table, CIHT. ETE uses CIHT to monitorsessions. The syntax of the CIHT parameter is:

CIHT=nnnnn

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

Table 1. 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 DRcontrol is disabled, even if theKETXCOUN exit is enabled in theCICS address space

between 1 and 1499 defaults to 1499

between 1500 and 99999 is converted to the nearest higherprime number


Recommended CIHT

We recommend that you specify:

CIHT = 2 * sessions

where sessions is your estimate of the number of sessions monitored by ETEat any one time.

For more information about the ETE EXEC statement in the ETE startupJCL, see “Customize ETE Startup JCL” on page 17.

CICS SEND Exit

ETE uses the standard CICS SEND exit, XZCOUT to control DR at the endof a logical transaction. Candle supplies the CICS exit moduleKETXCOUN.

You must enable this exit before starting response time collection for anyCICS resource. Failure to do so can result in session termination. See“Enabling/Disabling Exit by PLTPI/PLTSD.”

The exit applies to all CICS applications using 3270 VTAM terminals. It isinvoked every time a CICS SEND command is issued with only a negligibleincrease in instruction path length.

Enabling/Disabling Exit by PLTPI/PLTSD

The enabling/disabling processor is a Candle-supplied CICS command-levelapplication module.

After proper installation of this feature (see “Installation Considerations” onpage 39 and “CICS Table Updates Required” on page 39), you can use theCandle-supplied PLTPI module KETXCPLN to automatically enable theCandle-supplied CICS SEND exit at CICS startup. Likewise you can use thesame Candle-supplied module KETXCPLN in the PLTSD to automaticallydisable the exit at CICS shutdown.

Any confirmation or error messages from enabling/disabling appear as WTOmessages on the master console. See “Messages and Codes” on page 47.


Important

Candle recommends that you use this method for automaticallyenabling and disabling the CICS SEND exit.

Enabling/Disabling Exit by Transaction KETX

You can also use the Candle-supplied CICS transaction KETX to directlyenable or disable the Candle-supplied CICS SEND exit or to view the currentstatus of the exit:

KETX ENABLE Enables the CICS SEND exit.

Abbreviation is KETX E.

KETX DISABLE Disables the CICS SEND exit.

Abbreviation is KETX D.

KETX STATUS Displays the current status of the CICS SEND exit.

Abbreviation is KETX.

KETX DIAGNOSE Displays diagnostics if the CICS SEND exit is enabled.Initiate only if requested by Candle Customer Support.

Abbreviation is KETX DIAG.

Confirmation or error messages from KETX display at the initiating terminal.Refer to “Messages and Codes” on page 47.


Chapter 8. Problem Reporting

This chapter contains the procedure for gathering information about certainconditions or errors requiring assistance from Candle Customer Support. TheUser Response section of various ETE messages request that you collectsystems information and dumps before contacting Candle Customer Support.This enables Candle Customer Support to assist you in a timely and efficientmanner.

Please have the following information and data available before contactingCandle Customer Support:

1. Describe your system and network configurations.

Many network problems are directly related to network configuration.Since ETE resides in a host, network configuration also imposeslimitations on the capability of ETE. Identify the following items in theproblem report:

a. The subarea network configuration, where the VTAMs and NCPs arelocated, and how they are connected.

b. The location and type of the real terminal or terminals that areinvolved. What is the type of the terminal or terminals, are theylocally attached, remotely attached, or token ring? Is there amulti-session manager involved?

c. The system configuration of the Candle products that are running:

Á OMEGAMONÁ ETEÁ CL/SUPERSESSION

Are they on the same or different MVS systems?

d. The identity of similar products by other vendors.

2. Determine the software release and maintenance levels of both Candleand other vendor products.

3. Record all messages and codes.

Record ETE and OMEGAMON message numbers, return codes, andsense codes. Be sure to record any related VTAM, CICS, IMS, TSO, orCL/SUPERSESSION error messages. If the MVS console log, NetViewoperator log, master console log, or other logs are available, includethem.

Chapter 8. Problem Reporting 43

4. Obtain OMEGAMON debug screens, if available.

To obtain debug screens for OMEGAMON II for MVS orOMEGAMON II for CICS, enter this INFO-line command:

DEBUG

5. Save any dumps generated.

If ETE causes a storage dump in the MVS or VTAM subsystems or inETE itself, save this dump for problem analysis.

6. Request a non-destructive dump of ETE.

To request ETE to take a non-destructive dump, enter this commandfrom the MVS system console:

ETE DUMP

Note: This is an ETE command, not the MVS DUMP command.

7. Issue traces.

If you determine that the problem is related to data traffic, a terminal(s)hanging, incorrect data, or some other area of network operation, youneed 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 theOMEGAMON II for VTAM Internal Trace Feature. For GTFdescription see the IBMDiagnostics: Using Dumps and Traces (XAor ESA) manual or theDiagnostics: Service Aids (370) manual. Formore information on the OMEGAMON trace feature see theOMEGAMON II for VTAM User's Guide.

b. Start VTAM I/O and buffer traces. See the IBMACF/VTAMOperation manual.

Á If the problem is related to the real terminal and the user sessiondoesnot involve a multi-session manager, such asCL/SUPERSESSION, request VTAM traces for the real physicalterminal.

Á If the problem session does involve a virtual terminal, trace boththe real physical terminal and the destination host applicationsystem (such as CICS or TSO).

c. Recreate the problem situation while the trace is running.

d. Stop the GTF trace.


8. Issue CICS transaction KETX DIAGNOSE.

If you determine that the problem is related to CICS sessions or theCandle-supplied CICS SEND exit, issue the following transaction from aCICS terminal:

KETX DIAG

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

9. Copy the following data to tape and send to Candle Customer Support:

a. The portion of the master console log containing the output oftransaction KETX DIAG.

b. The raw dump and trace datasets.Do not send formatted dumps ortraces.

Chapter 8. Problem Reporting 45

Appendix A.Messages and Codes

This appendix contains all ETE messages, return codes, and sense codes.

| Messages

ETE0001 COMMAND NOT RECOGNIZEDExplanation: ETE recognized the ETE command, but the argument followingthe command was not valid.System Action: The command is not processed.User Response: Enter the ETE command followed by a valid ETE commandargument.

ETE0002 ETE Vvvvrr #nnLOADLIB= loadlibExplanation: This is a header line for the command output, identifying theETE version, whererr is a release identifier for versions that have more thanone release (for example, ETE101R2),vvv is the version number (for example,Version 500),nn defaults to 0,loadlib specifies the load library from which theETE modules were loaded.System Action: None.User Response: None. This is an informational message only.

ETE0003 COMPLETEExplanation: This is a trailer line for the command output, indicating that ETEcompleted the processing of the command. Note that the command output linessometimes appear on the MVS system log in a different order than ETEgenerated them. Even though this message is the last one produced by the ETEsubsystem in processing the command, other lines from the command outputmay appear after it on the log.System Action: None.User Response: None. This is an informational message only.

ETE0004 SUBSYSTEM INACTIVEExplanation: ETE is inactive as a result of an ETE QUIESCE command.Since most of ETE's storage was freed, most commands cannot be meaningfullyprocessed.System Action: The command is not processed.User Response: None. This is an informational message only.

Appendix A. Messages and Codes 47

ETE0005 COLLECTOR TRACE CAPTURE INSTALL FAILUREExplanation: The installation of the ETE capture facility subtask whichsupports the ETE response time collector's diagnostic trace function failed.System Action: ETE subsystem initialization continues.User Response: None. This is an informational message only.

ETE0010 CANDLE SCHEDULED CSA DUMP IN PROGRESSExplanation: The ETE dump was started.System Action: An SVC DUMP initiated.User Response: Wait for the dump to complete.

ETE0011 CANDLE SCHEDULED CSA DUMP COMPLETEExplanation: The ETE dump completed.System Action: The SVC DUMP for the ETE subsystem storage completed.User Response: Make a tape copy of the ETE dump from the SYS1.DUMPnndataset and contact Candle Customer Support as described in “ProblemReporting” on page 43.

ETE0013 VERBOSE MODE IS ALREADY ONExplanation: VERBOSE mode is already in effect; the VERBOSE argumentof the ETE command that was entered is discarded.System Action: None.User Response: None. This is an informational message only.

ETE0014 VERBOSE MODE IN EFFECTExplanation: VERBOSE mode is now in effect.System Action: ETE sends additional Application Program Interface (API)request messages and status to the system console.User Response: None. This is an informational message only.

ETE0015 VERBOSE MODE IS NOT ONExplanation: VERBOSE mode is not in effect; the NONVERBOSE argumentof the ETE command that was entered is discarded.System Action: None.User Response: None. This is an informational message only.

ETE0016 VERBOSE MODE IS OFFExplanation: VERBOSE mode was turned off.System Action: ETE operates in normal API mode.User Response: None. This is an informational message only.

ETE0017 COMMAND BUFFER COULD NOT BE ACQUIREDExplanation: A buffer in which to format an MVS MODIFY command to theETE address space to start the ETE diagnostic trace was not acquired.System Action: The ETE diagnostic trace is not started.User Response: Increase the REGION= parameter on the EXEC JCLstatement of the ETE address space JCL procedure. Then terminate and restartETE with the larger region.


ETE0018 ETE ADDRESS SPACE IS NOT EXECUTINGExplanation: The MVS MODIFY command to the ETE address space to startthe ETE diagnostic trace was not submitted because the ETE address space wasnot executing.System Action: The ETE diagnostic trace is not started.User Response: Restart the ETE address space. If the ETE address spaceabended, ensure that a dump was obtained by including a SYSMDUMP DDstatement in the ETE address space JCL procedure before calling CandleCustomer Support as described in “Problem Reporting” on page 43.

ETE0019 ADHT GETMAIN FAILUREExplanation: A GETMAIN for common storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0030 VERSION ## CMD PREF STATUS INST TYPEExplanation: This is a header line for the ETE0041 messages that follow.System Action: None.User Response: None. This is an informational message only.

ETE0031 Vvvvnn ETEvvvnn status typeExplanation: This is a detail line showing ETE system information. Thismessage repeats for each ETE subsystem installed in the MVS operatingenvironment. For each system, it shows:vvv Version number.nn Unique identifier (defaults to 0).vvvnn Command suffix.status Status:

ACTIVE ETE either currently has users or was installedstatically.

INACTIVE ETE currently has no users and has become dormant,freeing almost all storage and using almost no CPUcycles.

type Install type:DYNAMIC ETE will become inactive when the last user product

removes itself as an ETE user.STATIC ETE remains active until terminated with the ETE

QUIESCE command.System Action: None.User Response: None. This is an informational message only.

ETE0040 JOBNAME ASID TCB TYPEExplanation: This is a header line for the ETE0041 messages that follow.System Action: None.User Response: None. This is an informational message only.


ETE0041 job_name asid tcb_address user_typeExplanation: This message repeats for each product using the ETE subsystemprocessing the command. For each product, it shows:

Á jobname or started task nameÁ ASIDÁ TCB addressÁ ETE user type (CAPTURE or RSPTIME)

System Action: None.User Response: None. This is an informational message only.

ETE0042 NO USERS FOUNDExplanation: This message is a response to the ETE USERS command andindicates that ETE has no active request for product response time monitoring.System Action: None.User Response: None. This is an informational message only.

ETE0050 REMOVE REQUEST: RETURN CODE=nn, SENSE CODE=xxxxxxxxExplanation: In processing an ETE QUIESCE command, a REMOVE requestcreated:nn Non-zero return code. See “Return Codes” on page 62.xxxxxxxx Sense code. See “REMOVE request errors:” on page 68.System Action: The ETE quiesce process continues.User Response: Submit a copy of the MVS system log with this message, andany associated SVC DUMP and LOGREC data to Candle Customer Support.

ETE0051 QUIESCE COMPLETEExplanation: ETE removes itself from the MVS operating environment.System Action: None.User Response: Perform the activities that necessitated the removal of ETEfrom the MVS operating environment.

ETE0052 QUIESCE ALREADY IN PROCESSExplanation: An ETE QUIESCE command was received while processing of aprior QUIESCE command was still in progress.System Action: The later ETE QUIESCE command is ignored.User Response: Wait for the initial QUIESCE command to finish.

ETE0060 PRIVATE STORAGE GETMAIN FAILURE (CRWA)Explanation: A GETMAIN for private area storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Increase the REGION= parameter on the EXEC JCLstatement of the ETE address space JCL procedure; then terminate and restartETE with the larger region.


ETE0061 TCRB MAINTENANCE MODULE LOAD FAILUREExplanation: The load of the TCRB maintenance module from the ETEaddress space STEPLIB library failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Consult the MVS system log for the reason of the loadfailure.

ETE0062 COMMON STORAGE GETMAIN FAILURE (CRCB)Explanation: A GETMAIN for common storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0063 COMMON STORAGE GETMAIN FAILURE (CUWX)Explanation: A GETMAIN for common storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0064 COMMON STORAGE GETMAIN FAILURE (CUWH)Explanation: A GETMAIN for common storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0065 VTAM I/O BUFFER SIZE COULD NOT BE DETERMINEDExplanation: The VTAM I/O buffer size was not determined because VTAMcontrol blocks were either corrupted or changed by VTAM maintenance.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0070 THE FOLLOWING ETE COMMANDS ARE AVAILABLEExplanation: This is a header line for the output from the ETE HELPcommand.System Action: None.User Response: None. This is an informational message only.

ETE0071 ETE_help_information_detail_lineExplanation: This is a detail line of the output from the ETE HELP command.System Action: None.User Response: None. This is an informational message only.

ETE0072 SSTB SUBSYSTEM RESET SUCCESSFULExplanation: The ETE subsystem RESET command completed successfully.System Action: All ETE hooks into VTAM are completely withdrawn, and allETE storage that can be releases are released.User Response: None. This is an informational message only.


ETE0073 VTAM INTERFACES RESTOREDExplanation: This message confirms that the ETE subsystem RESETcommand withdrew all ETE hooks.System Action: All ETE hooks into VTAM have been completely withdrawn.User Response: None. This is an informational message only.

ETE0074 UNABLE TO RESTORE VTAM INTERFACESExplanation: The ETE subsystem RESET command was unable to withdrawETE's hooks, probably because additional hooks were established after ETE's.System Action: ETE subsystem RESET command processing terminates.User Response: None. This message is issued in conjunction with ETE0075.

ETE0075 RESET COMMAND NOT PERFORMEDExplanation: This message confirms that ETE subsystem RESET commandprocessing was unsuccessful.System Action: ETE subsystem RESET command processing terminates.User Response: Issue a system standalone dump and contact Candle CustomerSupport in accordance with “Problem Reporting” on page 43.

ETE0076 RESET NOT REQUIRED, SSTB SUBSYSTEM NOT FOUNDExplanation: The ETE subsystem RESET command determined that ETE'shooks were not present.System Action: ETE subsystem RESET command processing terminates.User Response: None. This is an informational message only.

ETE0078 ETE DIAGNOSTIC TRACE STARTEDExplanation: The ETE subsystem TRACEON command started the ETEdiagnostic trace function.System Action: Recording of ETE diagnostic trace entries into the ETEdiagnostic trace table commences.User Response: None. This is an informational message only.

ETE0079 ETE DIAGNOSTIC TRACE STOPPEDExplanation: The ETE subsystem TRACEOFF command stopped the ETEdiagnostic trace function.System Action: Recording of ETE diagnostic trace entries into the ETEdiagnostic trace table terminates.User Response: None. This is an informational message only.

ETE0080 ETE ADDRESS SPACE COMMAND ABENDEDExplanation: An abend occurred during the proccessing of an ETE subsystemcommand.System Action: The ETE subsystem command interface captures diagnosticinformation and recovers from the error.User Response: If the ETE subsystem command abends consistently, use theMVS DUMP command to dump the ETE address space and call CandleCustomer Support in accordance with “Problem Reporting” on page 43.


ETE0081 ETE ADDRESS SPACE STARTUP FAILED—NOT APF AUTHORIZEDExplanation: ETE address space startup failed because ETE library is notAPF-authorized.System Action: ETE address space startup task terminated.User Response: Make sure the ETE library is an APF-authorized library.

ETE0082 ETE ADDRESS SPACE STARTUP FAILED—RECOVERY COULD NOTBE ESTABLISHEDExplanation: ETE address space startup failed due to failure of the ESTAErecovery environment set up.System Action: The ETE address space startup task terminated.User Response: Obtain OMEGAMON debug screen outputs and contactCandle Customer Support for diagnosis in accordance with “Problem Reporting”on page 43.

ETE0083 ETE ADDRESS SPACE STARTUP FAILED—UNSUPPORTEDENVIRONMENTExplanation: ETE address space startup failed due to unsupported MVS orACF/VTAM environment.System Action: The ETE address space startup task terminated.User Response: Make sure that the ETE library is APF-authorized. Make surethat the ACF/VTAM started and is active. Make sure that the ACF/VTAMrelease level is Version 3.x.x or 4.x.x.

ETE0084 ETE ADDRESS SPACE STARTUP FAILED—INSUFFICIENT PRIVATESTORAGE AVAILABLEExplanation: ETE address space startup failed due to insufficient privatevirtual storage.System Action: The ETE address space startup task terminated.User Response: Increase private region size of the REGION parameter on theEXEC statement and restart the ETE startup task.

ETE0086 ETE ADDRESS SPACE TERMINATED BY SUBSYSTEM QUIESCEExplanation: The ETE address space was terminated as the result of an ETEQUIESCE command.System Action: The ETE address space is terminated and all allocated privateand ECSA storage is freed. All response time monitoring activities stop and allOMEGAMON products stop reporting response time data.User Response: This is an informational message only. You must restart theETE address space to resume response time monitoring.

ETE0087 ETE ADDRESS SPACE TERMINATED BY STOP COMMANDExplanation: The ETE address space was terminated as the result of a stopcommand received from the MVS console.System Action: The ETE address space is terminated and all allocated privateand ECSA storage is freed. Standard response time monitoring activitiesperformed by the OMEGAMON continue, but multi-session manager support isunavailable.User Response: This is an informational message only. You must restart theETE address space to resume multi-session manager support.


ETE0088 COMMAND ACCEPTEDExplanation: The MVS modify command entered from the system consolewas accepted.System Action: None.User Response: None. This is an informational message only.

ETE0089 COMPLETEExplanation: This is the output message trailer for an ETE address spacecommand.System Action: None.User Response: None. This is an informational message only.

| ETE0090 ETE STARTUP INSTALL REQUEST FAILED: RC= nn, SC=xxxxxxxx| Explanation: The request to statically install ETE, resulted in:| nn Non-zero return code. See “Return Codes” on page 62.| xxxxxxxx Sense code. See “INSTALL request errors:” on page 70.| System Action: ETE does not install.| User Response: Submit a copy of the MVS system log with this message, and| any associated SVC DUMP and LOGREC data, to Candle Customer Support.

ETE0091 ETE V500 SUCCESSFULLY INITIALIZEDExplanation: ETE was statically installed successfully. ETE will not becomeinactive when it has no users. You can deactivate ETE only with the ETEQUIESCE command.System Action: None.User Response: You can now start user products.

ETE0092 ETE V500 ADDRESS SPACE ALREADY EXECUTINGExplanation: The ETE Version 500 address space that just started isterminating because there already was an ETE Version 500 address space withthe same subsystem identifier started and running. Only one ETE Version 500address space with a specific subsystem identifier can run at a time.System Action: The ETE Version 500 address space that just startedterminates. The running ETE Version 500 address space is not affected.User Response: None. This is an informational message only.

ETE0093 VCHT GETMAIN FAILUREExplanation: The ETE address space startup task could not obtain storage forthe VCHT table from private virtual storage below the 16M line. The defaultREGION size value of your data center or the REGION size specified on theETE start up task JCL may be insufficient.System Action: The ETE address space terminates.User Response: Increase the REGION size and restart the ETE address space.


ETE0094 TRACE TABLE GETMAIN FAILUREExplanation: The ETE startup task could not obtain ECSA storage for thediagnostic trace table. The diagnostic trace is not required for normal ETEoperation.System Action: ETE address space initialization continues. However, thediagnostic trace is disabled.User Response: If the trace is needed for problem determination, make surethat enough ECSA storage is available and restart the ETE address space.

ETE0095 INVALID ETE ADDRESS SPACE COMMANDExplanation: The MVS modify command entered from the MVS console iseither not recognized or not supported.System Action: None.User Response: Make sure the command is valid and check the commandsyntax.

ETE0100 CANDLE job_name RSP EOT REMOVE REQUEST: RETURNCODE=nn, SENSE CODE=xxxxxxxxExplanation: A REMOVE request issued at end-of-task failed prior to tasktermination. The message shows:job_name

jobname or started task name of the user product.nn Non-zero return code. See “Return Codes” on page 62.xxxxxxxx Sense code. See “REMOVE request errors:” on page 68.System Action: None.User Response: Make a copy of the MVS system log with this message, andany associated SVC DUMP and LOGREC data. Contact Candle CustomerSupport in accordance with “Problem Reporting” on page 43.

ETE0101 ETE COULD NOT BE STARTED. VTAM NOT INITIALIZED ORVTAM IS AT AN UNSUPPORTED LEVEL.Explanation: ETE could not start because either VTAM was not initialized orVTAM was at an unsupported level.System Action: ETE discontinues initialization.User Response: If VTAM was not initialized, wait for VTAM to initialize andrestart ETE. If VTAM was already initialized, call Candle Customer Support.

ETE0110 ADD FAILED FOR luname—NO MULTISESSION MGR INFO PRESENTExplanation: This message appears only when the ETE subsystem is inverbose mode and an ADD request failed for a virtual terminal because ETE didnot collect any information about the virtual session between the virtual terminaland the application.System Action: The ADD request fails.User Response: None, if the ETE address space was started after IPL time andvirtual sessions already existed at the time that it was started.

If the virtual session for which no data exists was established after the ETEaddress space already began to execute, contact Candle Customer Support asdescribed in “Problem Reporting” on page 43.


ETE0111 ADD FAILED FOR luname—LU CURRENTLY IS IN CONCT STATEExplanation: This message appears only when the ETE subsystem is inverbose mode and an ADD request failed for a switched LU which is currentlynot connected to the network.System Action: The ADD request fails.User Response: None. This is an informational message only.

ETE0112 ADD REQUEST FAILED—ETE ADDRESS SPACE IS NOT EXECUTINGExplanation: This message appears only when the ETE subsystem is inverbose mode and an ADD request failed because the ETE address space is notexecuting.System Action: The ADD request fails.User Response: Restart the ETE address space. If the ETE address spaceabended, ensure that a dump was obtained by including a SYSMDUMP DDcard in the ETE address space JCL procedure before contacting CandleCustomer Support in accordance with “Problem Reporting” on page 43.

ETE0113 ETE request REQUEST FAILED: RC= xxxxxxxx, SC=xxxxxxxxExplanation: An automatic ADD or DELETE request invoked by the sessionmonitor facility failed with the reported return and sense codes. This message isissued only in verbose mode.System Action: The ADD or DELETE request fails.User Response: If the Session Monitor command abends consistently, usethe MVS DUMP command to dump the ETE address space and call CandleCustomer Support in accordance with “Problem Reporting” on page 43.

ETE0114 ATTACH OF COMMAND INTERFACE SUBTASK FAILEDExplanation: The ETE address space command interface subtask attach failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0115 ATTACH OF TCRB MAINTENANCE SUBTASK FAILEDExplanation: The ETE address space TCRB/XLE maintenance subtask attachfailed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.

ETE0116 IDENTIFY OF TCRB MAINTENANCE SUBTASK E.P. FAILEDExplanation: The ETE address space TCRB/XLE maintenance subtask entrypoint identify failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance with“Problem Reporting” on page 43.


ETE0117 ADD FAILED, SLU=sluname PLU=pluname RC=xxxxxxxx SC=xxxxxxxxExplanation: An ADD request failed for the reason specified in the displayedreturn code and sense code. This message is issued only in verbose mode.System Action: The ADD request fails.User Response: Respond as the return and sense codes indicate. See “ADDrequest errors:” on page 67.

| ETE0120 LOCATE FOR MODULE module_name ENTRY POINT entry_point_name| Explanation: A required VTAM module was successfully located.| System Action: :Processing continues.| User Response: None. This is an informational message only.

| ETE0121 LOCATE FOR MODULE module_name FAILED| Explanation: ETE was unable to locate a required VTAM module.| System Action: ETE startup fails.| User Response: Contact Candle Customer Support in accordance with| “Problem Reporting” on page 43.

| ETE0122 UNABLE TO LOCATE VTAM MODULE TABLE| Explanation: ETE experienced an internal error while locating a required| VTAM module.| System Action: ETE startup fails.| User Response: Contact Candle Customer Support in accordance with| “Problem Reporting” on page 43.

| ETE0123 KETAEVML GETMAIN FAILURE| Explanation: ETE was unable to getmain enough working storage.| System Action: ETE startup fails.| User Response: Increase the region parameter on the ETE startup JCL. If| symptom persists, contact Candle Customer Support in accordance with| “Problem Reporting” on page 43.

ETE0200 DR EXCLUSION LIST PROCESSING COMPLETE. RC=xxxxxxxxExplanation: ETE completed processing the device DR exclusion list optionfor the ETE address space.System Action: ETE address space initialization continues.User Response: See previous messages issued for diagnosis.

ETE0201 OPEN FAILED RKANPAR DATASET MEMBER mbrnameExplanation: ETE is unable to process member mbrname in the RKANPARpartitioned dataset because of an open error.System Action: ETE address space initialization continues.User Response: Determine the cause of the open error. For example, checkdataset specifications and security authorization.


ETE0202 DR EXCLUSION LIST KETXDLDR NOT FOUNDExplanation: ETE is unable to process the device DR exclusion list in theRKANPAR partitioned dataset because it was not found.System Action: ETE address space initialization continues.User Response: None.

ETE0203 I/O ERROR ENCOUNTERED PROCESSING RKANPAR DATASETMEMBER mbrnameExplanation: ETE is unable to process member mbrname in the RKANPARpartitioned dataset because an I/O error was encountered.System Action: ETE address space initialization continues.User Response: Determine cause of the I/O error. For example, check datasetspecifications and security authorization.

ETE0204 SYNTAX ERROR ENCOUNTERED PROCESSING DR EXCLUSIONLIST KETXDLDRExplanation: ETE is unable to process the device exclusion list in theRKANPAR partitioned dataset because of a device name specification error.System Action: ETE address space initialization continues.User Response: Ensure that member KETXDLDR in the RKANPAR PDS issyntactically correct.

ETE0205 ESQA STORAGE GETMAIN ERROR (DXLHT)Explanation: A GETMAIN request for ESQA storage failed.System Action: ETE address space initialization continues.User Response: Increase the ESQA storage and restart the ETE address space.

ETE0206 INVALID DXLHT ENCOUNTEREDExplanation: An internal logic error occurred in the ETE address space.System Action: ETE address space abends with U700.User Response: Consult the section “Problem Reporting” on page 43.

ETE0207 ESQA STORAGE GETMAIN ERROR (DXLHTE)Explanation: A GETMAIN request for ESQA storage failed.System Action: ETE address space initialization continues.User Response: Increase the ESQA storage and restart the ETE address space.

ETE0208 INVALID DXLHTE ENCOUNTEREDExplanation: An internal logic error occurred in the ETE address space.System Action: ETE address space abends with U701.User Response: Consult the section “Problem Reporting” on page 43.

ETE0209 DXLHTE=addressSLUNAME= slunameExplanation: Output display from the diagnostic command DUMPDXL whereaddress is the address of the DXLHTE andsluname is the SLUNAME of thedevice in the device exclusion list.System Action: None.User Response: None. This is an informational message only.


ETE0210 DR EXCLUSION LIST PROCESSING FAILED: RC= xxxxxxxxSC=xxxxxxxxExplanation: ETE is unable to process the device exclusion list in theRKANPAR partitioned dataset.

If RC=4, these sense codes are returned:X'00000004' Insufficient private memory. Increase the REGION=

parameter on the EXEC JCL statement of the ETE addressspace JCL procedure. Terminate and restart the ETE addressspace with the larger region.

X'00000008' RKANPAR partitioned dataset not allocated to the ETEaddress space.

X'0000000C' KETXDLDR not found in the RKANPAR partitioned dataset.

If RC=8, these sense codes are returned:X'00000004' Open failed for RKANPAR datset.X'00000008' I/O error occurred processing RKANPAR dataset.X'0000000C' Abend occurred processing RKANPAR dataset.X'00000010' ESTAE failed processing RKANPAR dataset.

If RC=C, these sense codes are returned:X'00000004' GETMAIN failed for DXLHT.

If RC=10, these sense codes are returned:X'00000004' GETMAIN failed for DXLHTE.X'00000008' Syntax error occurred while parsing KETXDLDR.X'0000000C' Abend occurred while parsing KETXDLDR.X'00000010' GETMAIN failed for private memory while parsing

KETXDLDR.X'00000014' ESTAE failed while parsing KETXDLDR.

System Action: ETE address space initialization continues.User Response: See previous messages issued for diagnosis.

ETE0211 RC=xxxxxxxx hexsluname length positionExplanation: Output display following ETE0204 output with the followingdiagnostic information.xxxxxxxx Return code which may be:

00000008 Internal error.0000000C Invalid SLUNAME specification.00000010 Invalid SLUNAME specification.00000014 Invalid SLUNAME specification.00000018 Internal error.0000001C Internal error.

hexsluname Hexadecimal representation of failing SLUNAME operand.length Length of failing operand.position Position of failing operand in KETXDLDR member data

record.System Action: None.User Response: None.


ETE0212 NO EXCLUDED DEVICES FOUNDExplanation: The DUMPDXL command was issued, but no excluded devicesare specified in the ETE address space.System Action: None.User Response: None. This is an informational message only.

ETE0220 ETE SUPPORT IN CICS ADDRESS SPACE (asid) IS ENABLEDGA(gwaaddr) GAL( gwalen).Explanation: CICS SEND exit (XZCOUT) for ETE support is enabled whereGA represents the address of the global work area, and GAL represents thelength of the global work area.System Action: None.User Response: None. This is an informational message only.

ETE0221 ETE SUPPORT IN CICS ADDRESS SPACE (asid) IS DISABLEDExplanation: CICS SEND exit (XZCOUT) for ETE support is disabled.System Action: None.User Response: None. This is an informational message only.

ETE0222 INVALID PARAMETER FOR KETX TRANSACTION IN CICSADDRESS SPACE (asid). SPECIFY ENABLE, DISABLE, OR STATUS.Explanation: User entered KETX with unrecognized parameter. The onlysupported parameters for this transaction are ENABLE, DISABLE, andSTATUS.System Action: Transaction is ignored.User Response: Reenter transaction with correct parameter.

ETE0223 ENABLING OF ETE SUPPORT IN CICS ADDRESS SPACE (asid) HASFAILED. RC( xxxx).Explanation: Error occurred during exit enable process. RC representsEIBRCODE value after CICS ENABLE command, which is documented in theCICS documentation set.System Action: CICS SEND exit is not enabled.User Response: Consult CICS documentation or notify your CICSadministrator. If the problem persists, contact Candle Customer Support.

ETE0224 DISABLING OF ETE SUPPORT IN CICS ADDRESS SPACE (asid) HASFAILED. RC( xxxx).Explanation: Error occurred during exit disable process. RC representsEIBRCODE value after CICS DISABLE command, which is documented in theCICS documentation set.System Action: CICS SEND exit is not disabled.User Response: Consult CICS documentation or notify your CICSadministrator. If the problem persists, contact Candle Customer Support.


ETE0225 ERROR WHEN EXTRACTING STATUS OF KETXCOUN EXIT IN CICSADDRESS SPACE (asid). RC(xxxx).Explanation: Error occurred during extraction of the status of ETE support inCICS. RC represents EIBRCODE value after CICS EXTRACT command,which is documented in the CICS documentation set.System Action: None.User Response: Consult CICS documentation or notify your CICSadministrator. If the problem persists, contact Candle Customer Support.

ETE0226 ERROR IN CIHT PARAMETER SPECIFICATIONExplanation: An invalid CIHT size value was entered in the PARM field onthe EXEC statement in the ETE startup JCL.System Action: ETE address space initialization continues. The default CIHTsize is used.User Response: Specify correct value for CIHT size and restart ETE if thedefault size is not sufficient.

ETE0227 SHUTDOWN CANNOT BE COMPLETED. DISABLE ETE SUPPORT INEVERY CICS ADDRESS SPACE. THEN REPLY 'Y' TO SHUTDOWN.Explanation: ETE shutdown routine detected that some CICS address spacesdid not free ETE resources at the request of ETE. This abnormal situation canhappen if a CICS address space with enabled ETE support abended.System Action: Waits for operator reply.User Response: Use CICS transaction KETX DISABLE in every CICSaddress space to disable ETE support. Then reply Y to allow ETE to terminate.If there are other active ETE address spaces, shut them down before disablingETE support in the CICS address spaces.

Enable ETE support in every CICS address space before restarting ETE.

ETE0228 CIHT GETMAIN FAILUREExplanation: GETMAIN for common storage above 16M failed.System Action: ETE address space and subsystem initialization is aborted.User Response: Contact Candle Customer Support in accordance withinstructions in “Problem Reporting” on page 43.

ETE0229 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxExplanation: Output display at initiating terminal and at master console fromCICS transaction KETX DIAGNOSE. The four hexadecimal values displayedare for Candle diagnostic purposes only.System Action: None.User Response: Give values to Candle Customer Support if requested.

ETE0230 ENABLING OF ETE SUPPORT IN CICS ADDRESS SPACE(asid) HASFAILED. CICS RELEASE nn IS NOT SUPPORTED.Explanation: ETE does not currently support CICS release nn.System Action: CICS SEND exit is not enabled.User Response: Contact Candle Customer Support in accordance with theinstructions in “Problem Reporting” on page 43.


Return Codes

The following table shows the return code as a decimal value followed bythe hexadecimal equivalent. Note that the sense codes apply only to returncodes 16 and 20.

Table 2. Return Codes

Decimal Hex Meaning

0 00 Request successfully completed.

4 04 ETE is not APF authorized.

8 08 Invalid handle.

12 0C ETE not active.

16 10 Maintenance mismatch. Sense code has first fix numbernot matching.

20 14 Request failed. Sense code has reason for failure.

24 18 Load of KETTINSN module failed. See MVS systemlog for reason.


Sense Codes

ETE sense codes are listed below.

ETE Address Space sense codes:

X'010000E0' Insufficient private storageX'010000E1' Unsupported operating environmentX'010000E2' Recovery not established

ETE Capture Facility ADD sense codes:

X'018001E0' Insufficient private storageX'018001E1' Unsupported environmentX'018001E2' Recovery not establishedX'018001E3' ETE is not runningX'018001E4' Unknown categoryX'018001E5' CRCA GETMAIN failureX'018001E8' CUWB lock obtain failureX'018001EA' RU capture facility is not upX'018001EB' CRCB build failureX'018001EC' Collector abendedX'018001ED' VIT PIU trace is inactiveX'018001EE' Abend occurred during requestX'018001EF' Load of KETTCAP stub failedX'018001F0' LU not found (Index into parm block is 12th bit for 1

byte)X'018001F1' Control block corruption detectedX'018001F2' CRCB entry length error

EXTRACT request errors:

These sense codes are returned by OMEGAMON messages.

X'020000C0' Insufficient private (NCWA)X'020000C1' Enqueue failureX'020000C2' User not monitoring this deviceX'020000C3' Dequeue failureX'020000C4' Control block corruption detectedX'020000C5' Abend occurred during requestX'020000C6' Collector abendedX'020000C7' Unsupported environmentX'020000C8' Recovery not established


X'020000C9' Lock obtain timeoutX'020000CA' VIT PIU trace is inactiveX'020000CB' Extract area specification errorX'020000CC' Extract area page fix errorX'020000CD' SLUL corruption detected during extract requestX'020000CE' SLUL is not active during extract requestX'020000CF' No terminal for extract requestX'020000D0' No partner for extract request

ETE Capture Facility REMOVE sense codes:

X'028001C0' Insufficient private storageX'028001C1' Unsupported environmentX'028001C2' Recovery not establishedX'028001C3' Collector abendedX'028001C4' VIT PIU trace is inactiveX'028001C5' Abend occurred during requestX'028001C6' ETE is not runningX'028001C7' CUWB lock obtain failureX'028001C8' Unable to locate CUWBX'028001C9' Subtask terminatedX'028001CA' Subtask did not terminateX'028001CB' REBF READY Q ENQ failedX'028001CC' Control block corruption detected

REFRESH request errors:


X'040000A0' Insufficient private (NCWA)X'040000A1' Enqueue failureX'040000A2' User not monitoring this deviceX'040000A3' Dequeue failureX'040000A4' Control block corruption detectedX'040000A5' Abend occurred during requestX'040000A6' Collector abendedX'040000A7' Unsupported environmentX'040000A8' Recovery not establishedX'040000A9' Lock obtain timeoutX'040000AA' VIT PIU trace is inactiveX'040000AB' SLUL corruption detected during refresh requestX'040000AC' SLUL is not active during refresh requestX'040000AD' No terminal for refresh requestX'040000AE' No partner for refresh request


ETE Capture Facility Install API sense codes:

X'048001A0' Insufficient private storageX'048001A1' Unsupported environmentX'048001A2' Recovery not establishedX'048001A3' ETE is not runningX'048001A4' CUWB GETMAIN failureX'048001A5' CRWA GETMAIN failureX'048001A7' KETTCAP ATTACH failureX'048001A8' CUWB lock obtain failureX'048001A9' PSQT overflowX'048001AA' RU capture facility is not upX'048001AB' CRCB build failureX'048001AC' Collector abendedX'048001AD' VIT PIU trace is inactiveX'048001AE' Abend during requestX'048001AF' Load of KETTCAP stub failedX'048001B0' LU not found (Index into PARM block is at the 12th bit of

1 byte)X'048001B1' Load of PIU delivery exit failed

STATUS request errors:


X'08000080' Insufficient private (NCWA)X'08000081' Enqueue failureX'08000082' User not monitoring this deviceX'08000083' Dequeue failureX'08000084' Control block corruption detectedX'08000085' Abend occurred during requestX'08000086' Collector abendedX'08000087' Unsupported environmentX'08000088' Recovery not establishedX'08000089' Lock obtain timeoutX'0800008A' VIT PIU trace is inactiveX'0800008B' KETTAPRN call to KETTSTSN failedX'0800008C' SLUL corruption detected during status requestX'0800008D' SLUL is not active during status requestX'0800008E' No terminal for status requestX'0800008F' No partner for status request


ETE Capture Facility sense codes:

X'08800180' Load failure for KETTCAPX'08800181' GM failure for KETTCAPX'08800182' Load failure for KETCAPIc API RTRX'08800183' GM failure for KETCAPIc API RTRX'08800184' Load failure for KETCAPIc APIX'08800185' GM failure for KETCAPIc APIX'08800186' Load failure for KETTCAPX'08800187' GM failure for KETTCAPX'08800188' Load failure for KETEPIDNX'08800189' GM failure for KETEPIDN

DELETE request errors:


X'10000060' Insufficient private (NCWA)X'10000061' Enqueue failureX'10000062' User not monitoring this deviceX'10000063' Dequeue failureX'10000064' Control block corruption detectedX'10000065' Abend occurred during requestX'10000066' Collector abendedX'10000067' Unsupported environmentX'10000068' Recovery not establishedX'10000069' Lock obtain timeoutX'1000006A' VIT PIU trace is inactiveX'1000006B' Lock obtain failureX'1000006C' CID not found during CIHT delete processingX'1000006D' ADPB not foundX'1000006E' No terminal for delete requestX'1000006F' No partner for delete request

RASTOP sense codes:

X'10800160' Insufficient private storageX'10800161' Enqueue failureX'10800163' VIT PIU trace is inactiveX'10800164' Collector abendedX'10800165' Abend occurred during requestX'10800166' Dequeue failureX'10800167' ETE address space is inactiveX'10800168' XMEM FREEMAIN failed (ADPB)X'10800169' XMEM services failedX'1080016A' ADPB lock obtain failure


X'1080016B' Recovery not establishedX'1080016C' ADPB not found for tokenX'1080016D' PSQE deletion failureX'1080016E' Lock obtain timeoutX'1080016F' SLUL corruption detected during STOPMON requestX'10800170' SLUL is not active during STOPMON request

ADD request errors:


X'20000040' Insufficient private (NCWA)X'20000041' Enqueue failureX'20000042' This sense code is returned for one of the following

reasons:

1. Device luname not found in network (no data providedfor VERBOSE WTO)

2. LU is a virtual terminal, but no information is availablefrom the MSM (see “Multi-Session Manager Interface”on page 25)

3. ETE address space is no longer running

4. LU is a switched LU or a 37xx TIC-attached tokenring LU that has a status of CONCT

Issue the ETE VERBOSE command to produce a WTO tothe system console each time this sense code is returned(except for reason 1 above). The WTO specifies which ofthe above reasons caused the failure.

X'20000043' Device not suitable for monitoringX'20000044' Device does not support SLU-PLU rspsX'20000045' User already monitoring this deviceX'20000046' Insufficient CSA—TDBAX'20000047' Insufficient CSA—TDBEX'20000048' Insufficient CSA—PSQEX'20000049' Dequeue failureX'2000004A' Control block corruption detectedX'2000004B' Abend occurred during requestX'2000004C' Collector abendedX'2000004D' Unsupported environmentX'2000004E' Recovery not establishedX'2000004F' Lock obtain timeoutX'20000050' Partner luname not found in networkX'20000051' VIT PIU trace is inactiveX'20000052' TCRB information is unavailableX'20000053' ETE address space is inactiveX'20000054' Device is in connectible status


X'20000055' Cross memory set up failureX'20000056' Add failed for LU type 1 or 3 device. (FAILNL2 was

specified on the EXEC statement in the ETE started taskJCL (TKANSAM member CANSET).)

X'20000057' No partner was specifiedX'20000058' Lock obtain timeoutX'20000059' CID not found during CIHT add processingX'2000005A' GETMAIN for additional CIHT failedX'2000005B' GETMAIN for ADPB failedX'2000005C' ADPB lock obtain failureX'2000005D' No terminal for add request

ETE Capture Facility QUIESCE sense codes:

X'20400240' Abend occurred during requestX'20400241' Collector abendedX'20400242' VIT PIU trace is inactiveX'20400243' Insufficient private storageX'20400244' Unsupported environmnetX'20400245' Recovery not establishedX'20400246' SRB GETMAIN failure

RASTRT sense codes:

X'20800140' Insufficient private storageX'20800141' Enqueue failureX'20800143' VIT PIU trace is inactiveX'20800144' Collector abendedX'20800145' Abend occurred during requestX'20800146' Dequeue failureX'20800147' ETE address space is inactiveX'20800148' XMEM GETMAIN failed (ADPB)X'20800149' XMEM services failedX'2080014A' ADPB lock obtain failureX'2080014B' Recovery not establishedX'2080014C' Parameter specification errorX'2080014D' Lock obtain timeoutX'2080014E' SLUL corruption detected during STARTMON requestX'2080014F' SLUL is not active during STARTMON request

REMOVE request errors:

These sense codes are returned by message ETE0050 or ETE0100 with areturn code of 16 or 20.


X'40000020' Insufficient private (NCWA)X'40000021' Enqueue failureX'40000022' Subsystem deactivation failureX'40000023' Dequeue failureX'40000024' Control block corruption detectedX'40000025' Abend occurred during requestX'40000026' Collector abendedX'40000027' Unsupported environmentX'40000028' Recovery not establishedX'40000029' Lock obtain timeoutX'4000002A' VIT PIU trace is inactiveX'4000002B' ETE address space is inactiveX'4000002C' ADPB deletion failed

ETE Capture Facility EXTRACT sense codes:

X'40400220' Insufficient private storageX'40400221' Unsupported environmentX'40400222' Recovery not establishedX'40400223' ETE is not runningX'40400224' CUHB validation errorX'40400225' CRWH validation errorX'40400226' Enqueue failureX'40400227' RUBF validation errorX'40400228' Size error, RUBF keptX'40400229' Collector abendedX'4040022A' VIT PIU trace is inactiveX'4040022B' Abend occurred during requestX'4040022C' Queue is nullX'4040022D' Subtask terminatedX'4040022E' Control block corruption detectedX'4040022F' Invalid token

CONNECT sense codes:

X'40800120' Insufficient private storageX'40800121' Enqueue failureX'40800122' Subsystem activation failureX'40800123' Insufficient CSA—SSWAX'40800124' Insufficient CSA—CLWAX'40800125' Insufficient CSA—SAHTX'40800126' Load failure—KETTCOLX'40800127' Insufficient CSA—KETTCOLX'40800128' Load failure—KETTHKScX'40800129' Insufficient CSA—KETTHKScX'4080012A' User already installed


X'4080012B' Insufficient CSA—PSQAX'4080012C' Dequeue failureX'4080012D' Control block detection detectedX'4080012E' Abend occurred during requestX'4080012F' Collector abendedX'40800130' Unsupported environmentX'40800131' Recovery not establishedX'40800132' Lock obtain timeoutX'40800133' VIT PIU trace is inactiveX'4080013F' ETE is not active on system

INSTALL request errors:

These sense codes are returned by message ETE0090 with a return code of16 or 20.

X'80000000' Insufficient private (NCWA)X'80000001' Enqueue failureX'80000002' Subsystem activation failureX'80000003' Insufficient CSA—SSWAX'80000004' Insufficient CSA—CLWAX'80000005' Insufficient CSA—SAHTX'80000006' Load failure—KETTCOLX'80000007' Insufficient CSA—KETTCOLX'80000008' Load failure—KETTHKScX'80000009' Insufficient CSA—KETTHKScX'8000000A' User already installedX'8000000B' Insufficient CSA—PSQAX'8000000C' Dequeue failureX'8000000D' Control block corruption detectedX'8000000E' Abend occurred during requestX'8000000F' Collector abendedX'80000010' Unsupported environmentX'80000011' Recovery not establishedX'80000012' Lock obtain timeoutX'80000013' Insufficient CSA—PSQTX'80000014' VIT PIU trace is inactiveX'80000015' CSA load failedX'80000016' No longer in useX'80000017' No longer in useX'80000018' No longer in useX'80000019' No longer in useX'8000001A' Load failure—RTAPIX'8000001B' Insufficient CSA—SSUVTX'8000001C' Insufficient CSA—RTAPIX'8000001E' ETE is not activeX'8000001F' TSC hook environment failureX'80000020' Cross-memory environment setup failed


X'80000021' Unable to obtain SSTB parameter list storageX'80xx0022' SSTB install problem (xx indicates the type of problem):

08 Caller is not APF-authorized0C Unable to obtain subpool 241 storage10 Unable to obtain subpool 228 storage14 Unable to obtain private work storage18 Caller is an unknown participant1C SSTB router module not found20 SSTB router module load failed24 SSTB installation failed, possible loop28 SSTB installation failed, VTAM inactive2C SSTB installation failed, unsupported environment

X'80xx0023' SSTB activation problem (xx indicates the type ofproblem):08 Caller is not APF-authorized0C Component routine address is invalid10 SSTB VTAM interface router was not installed14 Unable to obtain private work storage18 Caller is an unknown participant24 Component installation failed, possible loop28 Component installation failed, no slot

X'80xx0024' SSTB withdraw problem (xx indicates the type ofproblem):08 Caller is not APF-authorized0C Component routine address is invalid10 SSTB VTAM interface router was not installed14 Unable to obtain private work storage18 Caller is an unknown participant24 Component installation failed, possible loop28 Component installation failed, no slot

X'80000025' No longer in useX'80000026' Load failure for KETCAPIcX'80000027' GETM failure for KETCAPIc in SQAX'80000028' Load failure for KETCAPRNX'80000029' GETM failure for KETCAPRN in SQAX'8000002A' Load failure for KETCAPIcX'8000002B' GETM failure for KETCAPIc in SQAX'8000002C' Failed to establish environment at VITX'8000002D' Insufficient CSA—TSHTX'8000002E' Load failure for KETTTRCNX'8000002F' GETM failure for KETTTRCN in SQA

ETE Capture Facility DELETE sense codes:

X'80400200' Insufficient private storageX'80400201' Unsupported environmentX'80400202' Recovery not establishedX'80400203' Collector abended


X'80400204' VIT PIU trace is inactiveX'80400205' Abend occurred during requestX'80400206' ETE is not runningX'80400207' CUWB lock obtain failureX'80400208' Unable to locate CRCAX'80400209' Subtask terminatedX'8040020A' Subtask did not terminateX'8040020B' RUBF READY Q ENQ failedX'8040020C' Control block corruption detectedX'8040020D' Invalid token

XTAG sense codes:

X'80800100' Insufficient private storageX'80800101' Enqueue failureX'80800102' User not monitoring this deviceX'80800103' Dequeue failureX'80800104' Control block corruption detectedX'80800105' Abend occurred during requestX'80800106' Collector abendedX'80800107' Unsupported environmentX'80800108' Recovery not establishedX'80800109' Lock obtain timeoutX'8080010A' VIT PIU trace is inactiveX'8080010B' SLUL corruption detected during XTAG requestX'8080010C' SLUL is not active during XTAG requestX'8080010D' Call to KETTXTSN failedX'8080010E' No terminal for XTAG requestX'8080010F' No partner for XTAG request


Appendix B.Candle Customer Support

Introduction

Candle Corporation offers a comprehensive maintenance and support plan toensure you realize the greatest value possible from your Candle softwareinvestments. We have more than 200 technicians worldwide, committed toproviding you with prompt resolutions to your support requests.

Customer Support hours of operation are from 5:30 A.M. to 5:00 P.M.,Pacific Time. In the event of an after-hours or weekend emergency, Candle'scomputerized call management system ensures that a technician will returnyour call within one hour. For customers located outside of North America,after-hours and weekend support is provided by Candle Customer Supportlocations in the United States.

Electronic Support

Candle provides information and support services using

Á Candle's home page at www.candle.com. You can use the Candle Website to

– open problem records– access maintenance information– order products or maintenance– access IBM compatibility information– download fix packs for distributed products– read news and alerts– scan a list of scheduled Candle education classes

Á Candle Electronic Customer Support (CECS), an electronic customersupport facility. You can access this facility through the IBM GlobalNetwork. You can use CECS to

– open problem records– search our database for solutions to known problems– look for answers to commonly asked questions– read news and alerts– scan a list of scheduled Candle education classes

Both CECS and the Candle Web site are available 24 hours a day, 7 days perweek.

Appendix B. Candle Customer Support 73

Telephone Support

Our support network consists of product specialists who work with you tosolve your problem.

Candle uses an online problem management system to log and track allsupport requests. Your request is immediately routed to the appropriatetechnical resource.

When you call to report a problem, please have the following information:

Á your Candle personal ID (PID) number

Á the release level of the Candle product

Á the release level of IBM or other vendor software

Á identifying information and dates of recently applied maintenance to yourCandle product or IBM product

Á a detailed description of the problem (including the error message) andthe events preceding the problem

Á a description of any unusual events that occurred before the problem


Customer Support Phone Numbers

Telephone Fax

North America (800) 328-1811

(310) 535-3636 (310) 727-4204

Europe

Belgium/Luxembourg +32 (0) 3 270 95 60 +32 (0) 3 270 95 41

France +33 (0) 1 53 61 60 60 +33 (0) 1 53 61 06 16

Germany/Switzerland/Austria +49 (0) 89 54 554 333 +49 (0) 89 54 554 170

Italy - Freephone 800 80992

Netherlands +31 (0) 30 600 35 50 +31 (0) 30 600 35 10

Scandinavia +46 (0)8 444 5940 +46 (0)8 623 1855

U.K. +44 (0)161 437 5224 +44 (0)161 437 5225

(Southern Europe, Middle East and South Africa Agents call U.K.)

Asia Pacific - English Hub +61 2 9954 1818

Australia +61 2 8912 9898

Hong Kong 800 908 457

India +61 2 8912 9898

Indonesia 0018 03061 2061

Malaysia 1800 803 459

New Zealand 0800 449 596

Philippines 1800 1612 0096

Singapore 800 616 2075

Thailand 0018 00612 1045

Asia-Pacific - Japanese Hub +81 3 5562 6992 +81 3 5562 6995

Asia Pacific - Korean Hub +82 2 552 8744 +82 2 552 8746

Asia Pacific - Mandarin Hub +88 62 2739 3223 +88 62 2378 5993

Asia Pacific e-mail address: [email protected]

When your local support office is unavailable, you can contact Candle'sNorth America support center. If USADirect service is available in yourcountry, use the 800 telephone number. If USADirect service is notavailable, ask your international operator for assistance in calling Candle'slocal (310) number.

Appendix B. Candle Customer Support 75

Incident Documentation

You may be asked to send incident documentation to the Candle CustomerSupport Center. On the outside of all packages you send, please write theincident number given to you by the Customer Support representative.

Send tapes containing the incident information to the following address,unless directed otherwise by your Customer Support representative:

Candle Customer SupportCandle Support Center, Incident number2ð1 North Douglas StreetEl Segundo, CA 9ð245

Send all other relevant documentation, such as diskettes or paperdocumentation, to the address provided by your Customer Supportrepresentative.

Ensuring Your Satisfaction with Customer Support

Candle Customer Support is committed to achieving high customersatisfaction ratings in all areas. These include

Á connecting you to a support representative promptlyÁ providing you with the appropriate fixesÁ answering support questionsÁ filling your shipping ordersÁ supplying documentation

If you have a concern that has not been resolved to your satisfaction, you canopen a complaint ticket. All tickets are logged and tracked to ensureresponsiveness and closure. Using the ticket information, a manager willcontact you promptly to resolve your problem.


Index

A

actual PLU 27Adobe portable document format 8APF authorization 21audience 7

C

CA-MAZDAMON compatibility 14, 19Candle Electronic Customer Support (CECS) 73changing exclusion list 36CICAT 14CICS

DFH3465 message 37diagnosis via transaction KETX 45releases supported 38SEND exit 41session termination, preventing 37table updates 39

CICS definite responseCIHT parameter 18, 39, 40DFHPCT table 39DFHPPT table 39enabling/disabling exit 41EXEC keyword 39EXECKEY keyword 39EXITS keyword 39feature 37forcing 37graphic overview 38installation considerations 39KETX transaction 39KETXCPLN program 39MSM considerations 39PLTPI table 39PLTSD table 39releases supported 38SEND exit 41SIT table 39table updates required 39TASKDATAKEY keyword 39

CIHT parameter 18, 40CLRDUMP argument of ETE command 29

CL/SUPERSESSION 25, 27coexistence with other software 14coexistence with prior ETE releases 14concurrent ETE versions 23confirmation, KETX transaction 42contents of this manual 7conventions, documentation 9copies of ETE, multiple 23copy data to tape. 45CSA storage use 22CT/Engine Version 170 13customer service, problem reporting 43customer support 73customization for device exclusion 35

D

debug screens 44definite response

See also CICS definite responseforcing 12protection from 35protocol 11

device exclusion list 35DFH3465 message 37DFHPCT table 39DFHPPT table 39DIAGNOSE argument of KETX transaction 42,

45direct ETE command to ETE version 24DISABLE argument of KETX transaction 42disable CICS SEND exit 41documentation conventions 9domain, VTAM 27DUMP argument of ETE command 30DUMPDXL argument of ETE command 30

E

electronic customer support 73ENABLE argument of KETX transaction 42enable CICS SEND exit 41End-to-End

See ETE

Index 77

end-to-end response time 27application 12calculations 12CT/Engine requirement 13definite response protocol 11definition 11exception response protocol 12host 12, 27network 12, 27service to OMEGAMON 13terminals supported 13VTAM 12

error messages 47–61ETE 21

availability to OMEGAMON 21CIHT parameter 40coexistence with prior releases 14EXEC statement 40load library 21loading 21messages 47–61multiple copies 23non-destructive dump 44prerequisites 19preventing timeout 19recycling 22resetting 31return codes 62sense codes 63–72single system 14starting 17, 20stopping 21, 31TIME parameter 19verification 20, 21

ETE command 29–33arguments 29CLRDUMP argument 29direct to ETE version 24DUMP argument 30DUMPDXL argument 30HELP argument 30multiple ETE versions 24NOVERBOSE argument 30QUIESCE argument 17, 31RESET argument 31subsystem identifier 29syntax 29SYSTEMS argument 32TRACEOFF argument 32TRACEON argument 32USER argument 32

ETE command(continued)USERS argument 20, 33version number 24, 29

exception response protocol 12exclusion list 35

changing 36example 36KETXDLDR member 35RKANPAR dataset 18, 35

EXEC keyword 39EXEC statement 17, 39EXECKEY keyword 39EXITS keyword 39

F

FAILNL2 parameter 18FDRNL2 parameter 18forcing definite response 12, 37

G

GTF trace 44

H

HELP argument of ETE command 30host response time 27

I

identifying subsystems 23, 24, 29installation

CICAT 14CICS DR considerations 39instructions 14

J

JOB statement, TIME parameter 19


K

KETVTMnn ddname 24KETX transaction 39, 42, 45KETXCOUN exit module 41KETXCPLN program 39KETXDLDR member 35

L

LU types supported 13LU-LU sessions 25

M

major node recycling 22master console log 45message DFH3465, CICS 37messages

ETE 47–61MSM 21, 25

CICS definite response considerations 39customization 21ETE operations 27interface 25real terminals 26sessions 25VLUs 26

multiple copies of ETE 23multi-session manager

See MSMMVS

Command 54, 55STOP command 31system log information 48, 50, 55

N

NetSpy 14, 27Netview Performance Monitor

See NPM considerationsnetwork response time 12, 27NFDRNL2 parameter 17non-destructive ETE dump 44NOVERBOSE argument of ETE command 30NPM considerations 14, 24

O

OMEGAMONdebug screens 44ETE as service to 13VTAM trace facility 44

P

PCT table 39PLTPI table 41PLTSD table 41PLU 27portable document format, Adobe 8PPT table 39prerequisites to startup 19preventing

CICS session termination 37timeout 19

problem reporting 43protecting devices from DR 35protocol

definite response 11exception response 12violation 37

Q

QUIESCE argument of ETE command 31

R

real terminal 25, 26, 44recommended CIHT parameter 41recycling ETE 22recycling VTAM major node 22reporting problems 43RESET argument of ETE command 31response mode protocol violation 37response time

Seeend-to-end response timereturn codes 62RKANMOD dataset 21RKANPAR dataset

adding 18device exclusion list 18KETXDLDR member 18, 35

Index 79

RKETVTnn ddname 23RSPVTMnn ddname 23running concurrent ETE versions 23

S

SEND exit, CICS 41sense codes 63session switching message 21, 27session termination, preventing in CICS 37sessions, multiple 25single ETE system 14single VLU 25SIT table 39size of CIHT table 18, 40SNA LU types supported 13starting ETE 17, 20startup JCL 17STATUS argument of KETX transaction 42STEPLIB DD statement 21stopping ETE 21, 31storage considerations 31subsystem identifier 23, 24, 29subsystem status 32SVC

DUMP data 50, 55LOGREC data 50, 55

symbols, use of 10syntax, ETE command 29SYSTEMS argument of ETE command 32

T

table size parameter CIHT 18, 39table updates, CICS 39tape copy 45TASKDATAKEY keyword 39telephone support 74terminals supported 13TIME parameter, JOB statement 19timeout, preventing 19trace ETE

starting 32stopping 32

trace facility, OMEGAMON II for VTAM 44TRACEOFF argument of ETE command 32TRACEON argument of ETE command 32

traces for problem reporting 44transaction KETX 42

U

USER argument of ETE command 32USERS argument of ETE command 33

V

verifying startup 20version number 24, 29virtual logical unit

See VLUvirtual session switching 27virtual terminal 44Vital Signs, coexistence with 14VLU

configurationLU-LU 25multiple 26single 25

pool 25restrictions 27

VTAMdomain 27major node recycling 22PLU 27releases supported 13response time 12start list 19trace facility, OMEGAMON II 44

X

XZCOUT exit 41


end-to-end response time reference manual, v500

Documents