Tivoli OMEGAMON and IBM Tivoli Management Services on z/os

Transcription

1 Tioli OMEGAMON and IBM Tioli Management Serices on z/os Version End-to-End Response Time Feature Reference SC

2

3 Tioli OMEGAMON and IBM Tioli Management Serices on z/os Version End-to-End Response Time Feature Reference SC

4 Note Before using this information and the product it supports, read the information in Notices on page 39. This edition applies to ersion 6, release 2, modification 0 of IBM Tioli End-to-End Response Time Feature (product number HKET620 and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC and SC Copyright International Business Machines Corporation 1992, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Introduction New in this release Hardware and software requirements Terminal types supported z/os Communication Serer releases supported OMEGAMON XE monitoring agents on z/os supported Running ETE on a single system Coexistence with preious ersions Installing and configuring ETE Chapter 2. Understanding end-to-end response time How ETE calculates response time Chapter 3. Starting ETE Step 1: Shut down all OMEGAMON components that use ETE Step 2: Customize the ETE startup JCL Step 3: Add the RKANPARU dataset to the ETE startup JCL Excluding deices that cannot tolerate definite response protocol Step 4: Check the TIME parameter on the JOB statement Step 5: Start ETE Step 6: Verify that ETE has started correctly Step 7: Make ETE aailable to the OMEGAMON XE monitoring agents Step 8: Verify ETE and OMEGAMON operation Other ETE tasks Stopping ETE Recycling a major node Recycling ETE Customizing for a multi-session manager product Determining which products are using ETE serices Chapter 4. Running multiple copies of ETE Including DDNAME statements to identify ETE subsystems Issuing the ETE command with multiples instances of ETE running Running ETE with IBM Tioli NetView Performance Monitor Chapter 5. Customizing ETE to work with a multi-session manager MSM oeriew Operating ETE with MSMs Chapter 6. ETE commands ETE command syntax ETE command and arguments ETE CLRDUMP ETE DUMP ETE DUMPDXL ETE HELP ETE NOVERBOSE ETE QUIESCE ETE RESET ETE SYSTEMS ETE TRACEOFF ETE TRACEON ETE USER=userid Copyright IBM Corp. 1992, 2008 iii

6 ETE USERS Chapter 7. Creating a deice exclusion list Protecting deices from DR Defining the exclusion list Exclusion list example Changing the exclusion list Chapter 8. CICS definite response Solution proided Graphic oeriew CICS releases supported Multi-session manager considerations Installation considerations CICS table updates required ETE EXEC Parameter CIHT CICS SEND exit Enabling and disabling the exit using PLTPI or PLTSD Enabling and disabling the exit using transaction KETX Chapter 9. Reporting ETE problems Procedure for reporting a problem Chapter 10. ETE troubleshooting ABEND 0C4 receied with the ETE started task ABEND 0D6 when running with any OMEGAMON agent using ETE serices Definite response unit failures in VTAM, DB2, and CICS ETE address space abends with error code U ETE message ETE0101: ETE COULD NOT BE STARTED. VTAM NOT INITIALIZED OR VTAM IS AT AN UNSUPPORTED LEVEL logged ETE storage usage is excessie Multiple load attempts per day of ETE modules made trying to initialize the ETE subsystem OMEGAMON II for IMS Message OEI971 EPILOG/IMS ETE INSTALL FAILED ETE IS NOT ACTIVE logged OMEGAMON II for MVS message OM8389: RTA Not Operational. RC=20 RSC= E; RTA: TSO light is blue, meaning inactie OMEGAMON II for MVS message OM8389 RC=20 SC= A User Already Defined logged when ETE is restarted SMP/E message GIM35908I logged when installing OMEGAMON II for CICS and OMEGAMON XE for CICS Startup request failed with message ETE0090 logged Users signing on to TSO through a multi-session manager product are listed using the TSO HOST command but not the ETE USERS command Support for problem soling Using IBM Support Assistant Obtaining fixes Receiing weekly support updates Contacting IBM Software Support Determining the business impact Describing problems and gathering information Submitting problems Notices Trademarks i IBM Tioli OMEGAMON: ETE Reference

7 Index Contents

8 i IBM Tioli OMEGAMON: ETE Reference

9 Chapter 1. Introduction The IBM Tioli End-to-End (ETE ) Response Time Feature component captures end-to-end response time for applications that use either the definite response protocol or the response time exception response protocol, timing SNA traffic that flows through VTAM. ETE runs as a subsytem and OMEGAMON accesses ETE serices using API calls. The API calls are capable of determining whether or not the subsystem has an actie SSCVT entry. OMEGAMON XE monitoring agents can run without ETE being enabled. An OMEGAMON monitoring agent on z/os does not attempt to use ETE serices if the subsystem is not actie. This book proides the following information: A description of ETE An explanation of how to start ETE after installation and customization hae been completed A description of each ETE command argument. The ETE procedure is installed into your procedure library during Configuration Tool configuration. The configuration guide for each OMEGAMON monitoring agent on z/os that incorporates ETE describes the configuration process. For information on using ETE to monitor response time within a particular OMEGAMON agent, refer to the appropriate OMEGAMON agent documentation. This guide is for the z/os Systems Programmer/Analyst who is responsible for the following tasks: Installing applications, such as the ETE product Automating tasks on the system Monitoring new applications Troubleshooting and proiding solutions for operators when they hae problems This guide is also useful for the programmer analyst who is responsible for fine-tuning the performance of systems (by measuring system capabilities and tweaking configuration settings). Readers should be familiar with the following topics: The z/os operating system and its associated concepts UNIX System Serices TCP/IP and VTAM Performance monitoring concepts This chapter describes the End-to-End Response Time Feature (ETE), how it calculates response time, what is new in Version 6.2.0, and what hardware and software are supported. New in this release The following changes hae been made in ETE for this ersion: ETE has been reersioned from 560 to ETE has a new component FMID, HKET620. Updates since the.00 ersion of this book to do the following: Clarify usage issues with the new NFNDFC=NO parameter in Chapter 3 A new topic in Chapter 3, Determining which products are using ETE serices Updates to the troubleshooting chapter to document ABENDSA03 ETE Version is now configured using Configuration Tool ersion or later. Updates to the Configuration Tool hae introduced the following changes in the ETE installation procedures. Common configuration requirement for DFHRPL usage library and concatenation. Redesign of base runtime enironments and the runtime enironment load function. Copyright IBM Corp. 1992,

10 Executable code has been separated from the configuration data by the creation of a set of user libraries. This separation eliminates the need to reconfigure each product after applying maintenance through SMP/E, and allows runtime enironments sharing a base runtime enironment to hae more control oer their customized settings, such as security modules. A full or sharing runtime enironment now includes one or more of the following new user libraries, as required by the installed products: - RKANCMDU - RKANMODU - RKANPARU - RKANSAMU - RKANSQLU The Configuration Tool proides a utility to allocate the new user libraries during upgrade. The runtime enironment load process copies the target libraries to their user counterparts in runtime libraries in a base or a full runtime enironment. If the runtime enironment is set up to share the SMP/E target libraries directly, the load step is not required after applying SMP/E maintenance (unless the maintenance HOLDDATA information indicates otherwise). The redesign of the runtime enironment and the load function is aailable in a special programming enhancement (SPE). ETE now allocates the SSCVT control block using Key 0 CSA storage. Preiously, this control block was allocated using key 8. This fix addressed a security concern. Support for z/os ersion Support for CICS Transaction Serer for z/os Version 3.3, or later. Hardware and software requirements Terminal types supported ETE Version proides response time data for the following real LU types: SNA LU type 1 SNA LU type 2 SNA LU type 3 z/os Communication Serer releases supported ETE Version supports z/os ersion 1.8 (VTAM ersion 618), or higher. OMEGAMON XE monitoring agents on z/os supported ETE is an SNA response time monitor which runs as a subsystem. It proides a serice to OMEGAMON XE monitoring agents on z/os. ETE measures the host and network components of response time and furnishes them to any OMEGAMON that displays response time. Currently, the OMEGAMON products that obtain response time from ETE and their minimum supported leels are as follows: OMEGAMON XE for CICS, Version 3.1.0, or later OMEGAMON XE for IMS, Version 3.1.0, or later OMEGAMON XE for Mainframe Networks, Version 3.1.0, or later OMEGAMON XE on z/os, Version 3.1.0, or later Running ETE on a single system For all of the IBM Tioli OMEGAMON products that use ETE Version for response time, only one ETE Version system is required, regardless of the number of IBM Tioli OMEGAMON products you are running. 2 IBM Tioli OMEGAMON: ETE Reference

11 Coexistence with preious ersions ETE Version running in one address space can coexist with a preious ersion of ETE running in another address space. You can run multiple ETE subsystems for testing, but for production, use the minimum number of ETE systems required. For more information about running multiple ETE systems, see Chapter 4, Running multiple copies of ETE, on page 13. Installing and configuring ETE For each OMEGAMON XE monitoring agent on z/os that you want to use the ETE product, the ETE proc is installed into your proclib when you configure the product using the Configuration Tool. Your OMEGAMON monitoring agents should share the same ETE started task. For information about using the Configuration Tool, see the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide or the Configuration Tool online help. The chapters that follow explain how to further configure ETE for your site. Chapter 1. Introduction 3

12 4 IBM Tioli OMEGAMON: ETE Reference

13 Chapter 2. Understanding end-to-end response time End-to-end response time is the elapsed time between the moment that a user presses a key (Enter, F1 through F24, PA1, PA2, PA3, or Clear) and the moment that a response is receied at the terminal. For example, if you start a stopwatch when a user presses Enter and stop it when the terminal receies the application's first response to the user's request, the stopwatch shows the end-to-end response time for that request. To measure end-to-end response time, ETE places itself inside one of the VTAM SNA layers. In this location ETE can time all SNA traffic that flows through VTAM. End-to-end response time measurement requires that VTAM internal trace with the PIU option is actie. The measurement is started automatically when ETE is actiated. ETE captures end-to-end response time for applications that use either the definite response protocol or the response time exception response protocol. Definite response protocol: Under the definite response protocol, the application asks the terminal controller to respond to transmitted data by indicating whether or not the transmission was successful. The application must then wait for the controller s response before continuing. Because the controller responds to all transmissions, end-to-end response time is relatiely easy to monitor under the definite response protocol. Exception response protocol: Under the exception response protocol, the application asks the controller to respond only if an error occurs during data transmission to the terminal. Because ETE can measure end-to-end response time only for transactions that require a response from the controller, ETE must turn on definite response for applications that use the exception response protocol. After it measures the response time, ETE discards the definite response before it flows to the application. As a result, the application neer receies the definite response and is not een aware that a definite response was elicited How ETE calculates response time ETE measures the time between SNA eents from inside VTAM. The measured time begins when the request flows through VTAM toward the application; it ends when VTAM receies the definite response from the terminal controller. There is only one portion of end-to-end response time that ETE cannot capture directly and must estimate the time before the user's request reaches VTAM (T1 minus T0), as shown in Figure 1 on page 6: Copyright IBM Corp. 1992,

14 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 definite response to flow from the controller to VTAM (T6 minus T5). This time calculation is true because all definite responses and most inbound requests contain little data. Therefore, ETE calculates end-to-end response time as (T6 minus T1). 6 IBM Tioli OMEGAMON: ETE Reference

15 Chapter 3. Starting ETE Attention: Do not start ETE until you hae installed the component and customized it, as described in your OMEGAMON monitoring agent configuration guides. This chapter explains how to start ETE. For information on using ETE within your OMEGAMON monitoring agent, refer to the ETE information in your OMEGAMON monitoring agent on z/os configuration guides. To start ETE, use the following steps in sequential order. Step 1: Shut down all OMEGAMON components that use ETE To shut down OMEGAMON components that use ETE, complete the following steps. 1. Stop all started tasks that use ETE. To determine what tasks are running that use ETE, issue the ETE USERS command. See ETE USERS on page 20 for more information about this command. For information about stopping and starting specific started tasks, refer to the agent-specific conflagration guides. 2. Issue an ETE QUIESCE command to stop ETE. (See ETE QUIESCE on page 18 for details.) Step 2: Customize the ETE startup JCL The ETE startup JCL is named CANSETE. It is generated by the Configuration Tool when you configure ETE. Use this statement to control the monitoring of LU type 1 and 3 deices and ETE response to non-data flow control response units (RUs) issued by such programs as DB2. This is the format for the EXEC statement: EXEC PGM=KETESTRN,TIME=&tme PARM= 'pppppp,ciht=nnnnn' Where: TIME=&tme pppppp Is an optional parameter used to specify the maximum amount of time in minutes that a job step may use the processor or to find out through messages how much processor time a step used. Use the TIME parameter to increase or decrease the amount of processor time aailable to a job step oer the default alue. A step that exceeds its allotted time abnormally terminates and causes the job to terminate, unless an installation exit routine extends the time for the job. The exit routine IEFUTL is established through System Management Facilities (SMF). If you specify TIME=1440, the procedure neer times out. Is the control option parameter, one or more of the following, separated by commas: NFDRNL2 Monitor, but do not force DR on LU type 1 and 3 deices (default). This option allows collection of byte count information but not response time data for LU type 1 and 3 deices (unless the session is using DR of its own accord). FDRNL2 Monitor and force DR on LU type 1 and 3 deices. This option allows collection of byte count information and response time data for LU type 1 and 3 deices. Do not use this option with 3816 or 3820 printers. FAILNL2 Fail monitor requests for LU type 1 and 3 deices. Copyright IBM Corp. 1992,

16 This option preents collection of both byte count information and response time data for LU type 1 and 3 deices. NFNDFC=NO Forces definite response for non-data flow control response units (RUs)., This option enables ETE to force definite response for non-data flow control RUs. Change this parameter to NFNDFC=YES to preent the ETE subsystem from forcing definite response for non-data flow control RUs. You might want to code NFNDFC=YES if you experience failures in DB2 conersations such as when an SQL query passed to a DB2 application fails because the ETE subsystem has modified the response unit (RU) to force a definite response for a non-data flow control RU. Similarly, CICS may fail with the 0813 sense code for a BID bracket error. Again, coding NFNDFC=YES might fix this problem. Refer to Definite response unit failures in VTAM, DB2, and CICS on page 30 for information about identifying this DB2 error. Note: Regardless of the start parameter you use, it is recommended that ETE be started only once for the life of the IPL. Users of ETE serices must be able to access control blocks maintained by ETE. If ETE is not aailable continuously, users of its serices may suffer abends at termination such as ABENDSA03 If it becomes necessary for ETE to be stopped prior to an IPL, STOP all users of ETE serices before stopping the ETE started task. nnnnn CIHT table size for CICS definite response. (Chapter 8, CICS definite response, on page 23). Here is an example of this startup command: EXEC PGM=KETESTRN,TIME=&TME,PARM=',NFNDFC=YES' Step 3: Add the RKANPARU dataset to the ETE startup JCL To enable or disable other control options for the ETE address space, add the RKANPARU dataset to the ETE startup JCL. See Chapter 7, Creating a deice exclusion list, on page 21. Add the following statement directly after the EXEC PGM=KETESTRN statement: //RKANPARU DD DSN=hile.RKANPAR,DISP=SHR The RKANPARU dataset is where you specify information about enabling and disabling control options. If you do not add the RKANPARU dataset to the ETE startup JCL, no additional startup options (other than those on the EXEC statement) are processed. Excluding deices that cannot tolerate definite response protocol To exclude deices that cannot tolerate definite response protocol from ETE monitoring, complete the following steps: 1. Create member KETXDLDR in the RKANPARU library. 2. In member KETXDLDR, list the deices to exclude. You can refer to member KETXDLDR in the TKANSAM dataset which contains a sample deice exclusion list. 3. Ensure that the ddname RKANPARU is included in the ETE JCL. See Chapter 7, Creating a deice exclusion list, on page 21 for more information about excluding LU names from ETE monitoring. 8 IBM Tioli OMEGAMON: ETE Reference

17 ETE modifies the definite response bit so that it can calculate the response times for monitored terminals. The exclusion list tells ETE what not to monitor. If you hae applications that are sensitie to definite response, use the ETE exclusion list to preent any issues caused by ETE modifying the definite response bit. Step 4: Check the TIME parameter on the JOB statement The sample ETE started task JCL is shipped without a TIME parameter on the JOB statement. Many sites maintain a default TIME parameter alue (such as 1439 or 1440) that preents started tasks from timing out. If your site's default TIME parameter alue allows timeout, be sure to add an appropriate TIME parameter to the ETE JOB statement. The ETE started task must not timeout. Step 5: Start ETE Attention: Before you start ETE, ensure that you hae met these prerequisites: 1. Plan on running only one instance of ETE, regardless of the number of OMEGAMON XE monitoring agents or sessions are using ETE. 2. Ensure that VTAM is actie. 3. Because ETE must be actie before OMEGAMON can use it, plan to start ETE as soon as possible after VTAM initializes. If any sessions were started before ETE startup, those terminals' binding information are unaailable to ETE. This limits ETE's effectieness for those terminals. 4. ETE requires the VTAM internal trace to be running. ETE starts the trace automatically. 5. Verify that the STEPLIB DD statement in your OMEGAMON product JCL procedure points to the IBM Tioli OMEGAMON product runtime load library, RKANMODU, and is APF-authorized. 6. If you need to run concurrent ersions of ETE during an upgrade transition period, read Chapter 4, Running multiple copies of ETE, on page 13 before starting ETE. To start ETE, issue this command at the z/os operator console: S CANSET Where CANSET is the name of the ETE address space JCL procedure. This command results in the ETE Version address space remaining actie until it is QUIESCEd. To erify that ETE started successfully, look for this message on the operator console or in the MVS syslog: ETE0091 ETE VERSION 620 SUCCESSFULLY INITIALIZED Step 6: Verify that ETE has started correctly At a z/os console, enter the ETE USERS command to erify that ETE started. Check the command output that is displayed as shown in Figure 2 ETE USERS ETE0002: ETE V620 #00 LOAD DSN=hile.RKANMOD ETE0040: JOBNAME ASID TCB TYPE ETE0041: USER BE458 RSPTIME ETE0041: ETE EDB80 CAPTURE ETE0041: ETE EF1F8 CAPTURE ETE0041: ETE EF1F8 CAPTURE ETE0003: COMPLETE Figure 2. ETE USERS command output The first line of console output shows Chapter 3. Starting ETE 9

18 ETE ersion number Subsystem identifier (00 is the default) Load library from which you installed ETE The ETE started task name is displayed seeral times because ETE is a user of its own internal serices. Step 7: Make ETE aailable to the OMEGAMON XE monitoring agents To make ETE aailable to the OMEGAMON XE monitoring agents, you must set up all of your monitoring agents to load ETE modules from the hile.rkanmodu library. hile was defined during installation, as described in your OMEGAMON installation documentation. 1. Ensure that the IBM Tioli product load library, RKANMODU, is included in a STEPLIB DD statement for each of your OMEGAMON jobs and started tasks. This library contains OMEGAMON and ETE load modules. 2. Ensure that all libraries in the STEPLIB concatenation are APF-authorized. Step 8: Verify ETE and OMEGAMON operation To erify that ETE and your OMEGAMON XE monitoring agents are working correctly, complete the following steps: 1. Start eery OMEGAMON monitoring agent that uses ETE. 2. Verify ETE operation by starting response time monitoring for each OMEGAMON monitoring agent that is using ETE. Other ETE tasks In the course of ETE operation, you may need to perform these additional ETE tasks. Stopping ETE Keep ETE running continuously to collect session information history. If you decide to stop ETE for any reason, issue the ETE QUIESCE command as described in ETE QUIESCE on page 18. Recycling a major node If a VTAM major node containing logical units that are being monitored by OMEGAMON II for CICS or OMEGAMON II for IMS is recycled, you must quiesce ETE and restart it in order to re-establish linkage. OMEGAMON II for MVS and OMEGAMON II for Mainframe Networks are not affected by the recycle and do not need to re-establish linkage. Recycling ETE Keep ETE running for the life of the run. Howeer, 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 the component is restarted. Customizing for a multi-session manager product To obtain response time for sessions controlled by a multi-session manager product, you must configure the multi-session manager product to produce the session switch message. For more information, see Chapter 5, Customizing ETE to work with a multi-session manager, on page 15, Determining which products are using ETE serices There is no single command for determining which products are using ETE serices, but you can make this determination using the ETE USER and ETE USER=jobname commands. 10 IBM Tioli OMEGAMON: ETE Reference

19 First, issue the ETE USER command to show who the users of ETE serices are. In the example below, jobs V410ON (OMEGAMON II for Mainframe Networks) and V410ETE (ETE itself) are users of ETE serices, though the users could be any of the OMEGAMON monitoring agents that use ETE serices: NMPIPL27 ete users NMPIPL27 ETE0002: ETE V550 #00 LOAD - DSN=MFN.V4R1M0.RKANMOD NMPIPL27 ETE0040: JOBNAME ASID TCB TYPE NMPIPL27 ETE0041: V410ON DC0E0 RSPTIME NMPIPL27 ETE0041: V410ON DC0E0 CAPTURE NMPIPL27 ETE0041: V410ETE DF6A8 CAPTURE NMPIPL27 ETE0041: V410ETE DFE88 CAPTURE NMPIPL27 ETE0041: V410ETE DFE88 CAPTURE NMPIPL27 ETE0003: COMPLETE Next, use the information returned in the JOBNAME field to issue a second command for details about a specific job: ETE USER=jobname, where jobname is one of the jobnames returned by the ETE USER command. For example, the ETE USER=410on command returns the following details about the V410on job: NMPIPL27 ete user=410on NMPIPL27 ETE0002: ETE V550 #00 LOAD - DSN=MFN.V4R1M0.RKANMOD NMPIPL27 ETE0043: V410ON : ASCB=00FC7A00, - TCB=006DC0E NMPIPL27 ETE0044: NTCP0001/NT9DT002 NTCP0002/NT9DT003 - NTCP0003/NT9DT NMPIPL27 ETE0044: NTCP0004/NT9DT005 NTCP0005/NT9DT006 - NTCP0006/NT9DT NMPIPL27 ETE0044: NTCP0007/NT9DT008 NTCP0008/NT9DT NMPIPL27 ETE0003: COMPLETE Chapter 3. Starting ETE 11

20 12 IBM Tioli OMEGAMON: ETE Reference

21 Chapter 4. Running multiple copies of ETE Under normal conditions, running multiple OMEGAMON XE monitoring agents requires only one copy of ETE. During test, product migration, or under special circumstances, you may need to start seeral copies of ETE Version or Version and prior releases. This chapter describes considerations for running multiple copies of ETE. You can run any of the following configurations: Multiple copies of ETE Version Multiple copies of a prior ETE release Version and a prior ETE release When using multiple copies, to identify and run a specific copy of ETE ersion you must complete the following sections. Including DDNAME statements to identify ETE subsystems When using multiple copies of ETE, run the following command g to identify and run a specific copy of ETE Version You must include the following DD statement in each ETE PROC: //RKETVTnn DD DUMMY Where nn is a unique numeric suffix between 00 and 15, identifying the subsystem. A maximum of four ETE address spaces can run concurrently in a single domain. Attention: To identify the ETE subsystem to the OMEGAMON monitoring agent that is using it, be sure to also include the DD DUMMY statement, as described preiously, in the OMEGAMON PROC. Issuing the ETE command with multiples instances of ETE running To direct ETE commands to the correct ETE when more than one ETE system is running, include the ersion number in the command string, using the following command syntax: ETEnnn:cccccccc Where nnn is the three-digit ETE ersion number or two-digit subsystem identifier and cccccccc is the command you are issuing. For example, to QUIESCE ETE Version 6.2.0, issue this command: ETE620 QUIESCE Running ETE with IBM Tioli NetView Performance Monitor These are special operational considerations when running concurrent ETEs and the IBM Tioli NetView Performance Monitor (NPM) product. ETE can coexist with NetView Performance Monitor. When NetView Performance Monitor starts, it disregards any existing interface participant and installs itself as the only front-end interface to VTAM. This disables ETE operation. ETE detects this condition and reinstalls itself in conjunction with NPM. When NetView Performance Monitor stops, it remoes itself as an interface participant but does not ensure the integrity of other interface participants. ETE also detects this condition and recoers from it. If NetView Performance Monitor starts or stops when more than one ETE system is running, only one ETE recoers. The ETE that recoers depends on arious factors at the time the eent occurs. The ETE that does not recoer does not hae an impact on the system, but does not report response time information. Copyright IBM Corp. 1992,

22 Note: Running multiple copies of ETE with NetView Performance Monitor in your production enironment is not recommended because of the limitations stated preiously. 14 IBM Tioli OMEGAMON: ETE Reference

23 Chapter 5. Customizing ETE to work with a multi-session manager This chapter describes how ETE interacts with multi-session managers (MSMs). MSM oeriew In a configuration with an MSM, such as IBM CL/SUPERSESSION, a terminal user logs onto the MSM using a real terminal. Then, using a pool of Virtual Logical Unit (VLU) names, the MSM establishes sessions on behalf of that real terminal. Depending on the MSM implementation, you can use the following VLU configurations to support multiple logical unit-logical unit (LU-LU) sessions: The MSM establishes multiple sessions on behalf of a real terminal using a single VLU, as shown in Figure 3: Figure 3. MSM configuration: real terminal using a single VLU The MSM establishes multiple sessions on behalf of a real terminal using multiple VLUs, as shown in Figure 4: Figure 4. MSM configuration: real terminal using a multiple VLUs The MSM establishes multiple sessions on behalf of multiple real terminals using a single VLU, as shown in Figure 5 on page 16: Copyright IBM Corp. 1992,

24 Figure 5. MSM configuration: multiple real terminals using a single VLU In each of the preceding configurations, ETE Version measures the host and network components of response time in one of the following two ways: As host response time, the time it takes for the data to flow between the application (CICSA, CICSB, TSO) and the VLU. As network response time, the time it takes for the data to flow between the MSM and the real terminals (TERMA, TERMB). Operating ETE with MSMs The following conentions apply to ETE operation with MSMs: Both ETE and the MSM must be located in the same VTAM domain. ETE supports MSMs that use the irtual session switching conention proposed by Computer Associates International. MSMs that follow this conention produce a non-display 3270 data stream message that is sent to the physical terminal each time a session switch is performed. This is the session switch message. Many MSMs (including the IBM CL/SUPERSESSION product), support this conention. There is typically an exit program for the MSM that must be enabled in order to support the irtual session switching conention. When using ETE through OMEGAMON II for Mainframe Networks, the actual PLU of the irtual session (such as CICS, IMS, or TSO) can be the same domain, across domains, or een across networks. You must start ETE prior to any MSM containing irtual logical units (VLUs) that ETE will monitor. ETE does not monitor MSM sessions if it is unaware of the VLU and real terminal relationship. If you cancel or stop the ETE address space, response time numbers are no longer accurate and subsequent attempts to monitor terminals might fail until the next restart of the MSM. The path information units (PIUs) for the session switch datastream do not trael across domains. Therefore VLUs that establish a TSO session on an LPAR other than the LPAR on which the MSM is running will not be monitored by the ETE that is running in the LPAR in which the TSO session is established. 16 IBM Tioli OMEGAMON: ETE Reference

25 Chapter 6. ETE commands This chapter describes the ETE operator command. The command syntax is defined, all command arguments are listed alphabetically with a brief description of their function, and the resulting console output is illustrated. ETE command syntax Issue the ETE operator console command using the following syntax: ETEnnn cccccccc Where: nnn Is the three-digit ETE ersion number (such as 620) or two-digit ETE subsystem identifier (a unique number between 00 and 15). This suffix is only required when running multiple copies of ETE. For more information, see Chapter 4, Running multiple copies of ETE, on page 13. cccccccc Is the ETE command argument ETE command and arguments ETE accepts the ETE operator console command with an argument. The ETE command with each of its alid arguments is shown below. ETE CLRDUMP Command: ETE CLRDUMP Function: Resets the flag that indicates dumps hae been completed, which allows additional memory dump collection. Sample: ETE CLRDUMP ETE0002: ETE V620 #00 LOAD DSN=hile.RKANMODU ETE0003: COMPLETE ETE DUMP Command: ETE DUMP Function: Creates an SVC memory dump tailored for ETE problem analysis and troubleshooting. Sample: ETE DUMP ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0010: OMEGAMON SCHEDULED CSA DUMP IN PROGRESS ETE0011: OMEGAMON SCHEDULED CSA DUMP COMPLETE ETE0003: COMPLETE ETE DUMPDXL Command: ETE DUMPDXL Function: Displays the excluded deices. Sample: Copyright IBM Corp. 1992,

26 ETE DUMPDXL ETE0002: ETE V620 #00 LOAD DSN=hile.RKANMODU ETE0209: DXLHTE=014A70A8 SLUNAME=DUMMYA ETE0209: DXLHTE=014A7980 SLUNAME=DUMMYB ETE0003: COMPLETE ETE HELP Command: ETE HELP Function: Displays aailable ETE subsystem command arguments. Sample: ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0070: THE FOLLOWING ETE COMMANDS ARE AVAILABLE: ETE0071: CLRDUMP -- RESET DUMP FLAG/ALLOW NEW DUMP ETE0071: DUMP -- PRODUCE A DIAGNOSTIC ETE SVC DUMP ETE0071: DUMPDXL -- LIST EXCLUDED DEVICES ETE0071: HELP -- PRODUCE THIS DISPLAY ETE0071: QUIESCE -- TERMINATE THE ETE SUBSYSTEM ETE0071: RESET -- RESET ETE SUBSYSTEM AND QUIESCE ETE0071: SYSTEMS -- DISPLAY ETE SUBSYSTEM INSTALLED ETE0071: TRACEON -- START ETE DIAGNOSTIC TRACE ETE0071: TRACEOFF -- STOP ETE DIAGNOSTIC TRACE ETE0071: USER= -- DISPLAY LUNAMES MONITORED BY A SPECIFIC PRODUCT ETE0071: USERS -- DISPLAY PRODUCTS USING THE ETE SUBSYSTEM ETE0071: VERBOSE -- PRODUCE A DIAGNOSTIC WTO FOR SELECTED EVENTS ETE0071: NOVERBOSE -- CANCEL EFFECTS OF VERBOSE COMMAND ETE0003: COMPLETE ETE NOVERBOSE Command: ETE NOVERBOSE Function: Cancels the effect of the ETE VERBOSE command. VERBOSE MODE OFF is the default status. Sample: ETE NOVERBOSE ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0003: COMPLETE.RKANMODU ETE0016: VERBOSE MODE OFF ETE0003: COMPL ETE ETE QUIESCE Command: ETE QUIESCE Function: Shuts down ETE. Use this command before applying maintenance and restarting ETE. After ETE shuts down, OMEGAMON receies a return code or sense code indicating that ETE is not operational. QUIESCE does not impact other network monitoring components or products. Stopping the ETE address space using the MVS STOP command automatically generates an ETE QUIESCE command. CAUTION: A small amount of common storage is intentionally left behind and is re-used when ETE is restarted. Do not free this storage with the CSA Analyzer because this is not orphan storage. Stop ETE only when necessary. It is best to start ETE immediately after VTAM startup and keep ETE running continuously to collect session information history. 18 IBM Tioli OMEGAMON: ETE Reference

27 Before stopping ETE with automation, the shutdown of OMEGAMON regions must be complete. An ABEND0C4 is issued if you fail to shut down OMEGAMON regions before issuing the ETE QUIESCE command. The automation procedure must check that no ETE users are actie before the ETE QUIESCE is issued. Sample: ETE QUIESCE ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0003: COMPLETE.RKANMODU ETE0051: QUIESCE COMPLETE ETE0003: COMPLETE ETE RESET Command: ETE RESET Function: Use this command only at the direction of IBM Software Support. Resets VTAM interfaces and quiesces ETE subsystem and address space. ETE RESET impacts OMEGAMON and other network monitoring systems. Attention: Use this command only at the direction of IBM Software Support. Sample: ETE RESET ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0003: COMPLETE.RKANMODU ETE0072: SSTB SUBSYSTEM RESET SUCCESSFUL ETE0073: VTAM INTERFACE RESTORED ETE0003: COMPLETE ETE SYSTEMS Command: ETE SYSTEMS Function: Displays ETE subsystem status. Sample: ETE SYSTEMS ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0030: VERSION ## CMD PREF STATUS INST TYPE ETE0031: V ETE50000 ACTIVE STATIC ETE0003: COMPLETE ETE TRACEOFF Command: ETE TRACEOFF Function: Stops ETE problem determination diagnostic trace. Trace off is the default status. Sample: ETE TRACEOFF ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0079: ETE DIAGNOSTIC TRACE STOPPED ETE0003: COMPLETE ETE TRACEON Command: ETE TRACEON Function: Starts ETE problem determination diagnostic trace. Sample: Chapter 6. ETE commands 19

28 ETE TRACEON ETE0002: ETE V620 #00 LOADLIB=hile.RKANMODU ETE0078: ETE DIAGNOSTIC TRACE STARTED ETE0003: COMPLETE ETE USER=userid Command: ETE USER=userid Function: Displays all LU names being monitored by the specific product using ETE. userid is a job name as shown in the ETE USERS command display Sample: ETE USER=USER001 ETE0002: ETE V620 #00 LOAD DSN=hile.RKANMODU ETE0040: USER001 : ASCB=00EE9080, TCB=007C5458 ETE0044: L /TSOG0021 L /SMVTAMG L /RGSS001N ETE0044: L613A45 /V146GTW1 L613A74 /OIVTAMG0 L /SUPGATEG ETE0044: L615A106/V146GTW1 L635 /TSOG0028 ETE0003: COMPLETE ETE USERS Command: ETE USERS Function: Shows the STCNAME or JES JOBNAME, ASID, and TCB address of each product using ETE. Sample: ETE USERS ETE0002: ETE V620 #00 LOAD DSN=hile.RKANMODU ETE0040: JOBNAME ASID TCB TYPE ETE0041: USER BE458 RSPTIME ETE0041: ETE EF1F8 CAPTURE ETE0041: ETE EF1F8 CAPTURE ETE0003: COMPLETE 20 IBM Tioli OMEGAMON: ETE Reference

29 Chapter 7. Creating a deice exclusion list This chapter describes a feature of ETE you can use to exclude deices from ETE monitoring, een though they hae been defined for monitoring by one or seeral OMEGAMON products. This exclusion takes effect whether OMEGAMON defined specific or generic SLU deices for monitoring. Protecting deices from DR Although you use ETE to monitor response time for VTAM applications in session with SLU deices, you can exclude SLU deices that are not tolerant of the definite response (DR) requests issued by ETE. To do this, set up a deice exclusion list specifying those SLUs that you want to exclude from DR requests. The SLUs in the list are defined in the ETE 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 the RKANPARU dataset. You can refer to the sample KETXDLDR member in the TKANSAM dataset. Use the following syntax to define the exclusion list: Card columns 1 71 An asterisk (*) in column 1 indicates a comment line, all information on that line is ignored. Note: An asterisk (*) in column 1 indicates a comment line. All information on a line containing as asterisk is ignored. Rules: 1. You can code more than one deice on one line, separated by commas or blanks. 2. Wildcards, masks, and generic deice names are not supported. See Step 3: Add the RKANPARU dataset to the ETE startup JCL on page 8 for information about RKANPARU in the ETE JCL. Exclusion list example The following example shows how KETXDLDR excludes SLUs from monitoring by ETE. ************************************************************************ * MEMBER: KETXDLDR * * * * FUNCTION: SAMPLE DR DEVICE EXCLUSION LIST * * * ************************************************************************ DEVICE DEVICE02 DEVICE DEVICE04,DEVICE Changing the exclusion list You can change the deice exclusion list in the KETXDLDR member of the RKANPARU dataset at any time. To implement the changes, you must recycle (stop and then restart) ETE. Refer to ETE QUIESCE on page 18 for information about stopping and restarting ETE. Copyright IBM Corp. 1992,

30 22 IBM Tioli OMEGAMON: ETE Reference

31 Chapter 8. CICS definite response This chapter describes a feature of ETE Version that preents immediate response mode protocol iolations during CICS sessions. To monitor response time, ETE may change an exception response to a definite response. If this response is immediately followed by another PIU with definite response requested, the CICS session may experience an immediate response mode protocol iolation (sense code X 200A ). By proiding a CICS SEND exit, this feature ensures that the first request is answered before the second request is sent, thus preenting CICS session termination (DFH3465). The IBM-supplied CICS SEND exit forces definite response only when all of the following 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 proided To support CICS definite response mode, IBM supplies the following: Module KETXCOUN for the standard CICS SEND exit XZCOUT Enabling and disabling of the CICS SEND exit in two forms: PLTPI/PLTSD module KETXCPLN to enable the exit at CICS startup and disable the exit at CICS shutdown CICS transaction KETX to directly enable or disable the exit Parameter CIHT on the ETE EXEC statement to specify the CIHT table size Graphic oeriew Figure 6 on page 24 illustrates the ETE-CICS definite response implementation. Copyright IBM Corp. 1992,

32 Figure 6. ETE DR Implementation for CICS CICS releases supported Because this feature uses a CICS exit, ETE is now CICS release sensitie. ETE is supported for CICS Transaction Serer Version 2.3 and higher with the CICS user exit program. Multi-session manager considerations If you are using a multi-session manager (MSM) to log onto CICS, the MSM and ETE must be in the same domain as CICS. Installation considerations You must include the IBM Tioli product load library, xkanmod, in STEPLIB and xkanmodr in the DFHRPL concatenations of the CICS startup JCL. For enironments where you plan to run a mix of OMEGAMON XE ersion 4.2.0, ersion 4.1.0, and ersion releases on the same LPAR, install the ETE ersion requisite APAR OA20701 in the CSI where ersion or ersion or both are installed prior to installing ETE ersion ETE ersion APAR OA20701 is required if you plan to run mixed releases OMEGAMON agent on the same LPAR (n, n-1, and n-2). The OMEGAMON XE ersion products that are included with ETE ersion 500 cannot communicate with ETE Version 620. You must continue to run ETE ersion 500 in addition to ETE ersion on the same LPAR if you plan to run a mixture of ersion 221 agents and ersion 420 agents on the same LPA. The CIHT parameter is located on the ETE EXEC statement. You may choose not to enable this feature by specifying CIHT=0. For more information on the CIHT parameter, see ETE EXEC Parameter CIHT on page 25 and Step 2: Customize the ETE startup JCL on page IBM Tioli OMEGAMON: ETE Reference

33 CICS table updates required Before you can initialize ETE support components in the CICS address space, you must modify sample CSD definitions files in TKANSAM that are included with ETE. These sample jobs are found in the following locations and perform the functions described in the following sections:: &thile.tkansam(ketcsdj) A sample job to update the CSD definitions. &thile.tkansam(ketcsd) The CSD Definitions to delete old ersions and define the new entities. If you prefer to use transaction CEDA to define resources online, do the following: 1. Define transaction KETX with the same tranaction definitions specified in the sample CSD defintion found in &thile.tkansam(ketcsd). If you migrate resource definitions from a prior CICS release, make sure that the migrated definitions match those found in the KETCSD sample definition. 2. Define programs KETXCPLN and KETXCOUN with the same program definitions specified in the sample CSD definition found in &thile.tkansam(ketcsd). ETE EXEC Parameter CIHT CIHT is the parameter on the ETE EXEC statement you use to specify the number of entries in the ETE table, CIHT. ETE uses CIHT to monitor sessions. The syntax of the CIHT parameter is: CIHT=nnnnn The following table shows the effects of the possible CIHT settings. If CIHT is... Then CIHT... Omitted Defaults to 1499 Between 0 and Is within alid range Zero Is not allocated and CICS DR control is disabled, een if the KETXCOUN exit is enabled in the CICS address space Between 1 and 1499 Defaults to 1499 Between 1500 and Is conerted to the nearest higher prime number Specify the following: CIHT=2*sessions Where sessions is your estimate of the number of sessions monitored by ETE at any one time. For more information about the ETE EXEC statement in the ETE startup JCL, see Step 2: Customize the ETE startup JCL on page 7. CICS SEND exit ETE uses the standard CICS SEND exit, XZCOUT, to control DR at the end of a logical transaction. IBM supplies the CICS exit module KETXCOUN. You must enable this exit before starting response time collection for any CICS resource. Failure to do so can result in session termination. See Enabling and disabling the exit using PLTPI or PLTSD on page 26. The exit applies to all CICS applications using 3270 VTAM terminals. It is inoked eery time a CICS SEND command is issued with only a negligible increase in instruction path length. Chapter 8. CICS definite response 25

34 Enabling and disabling the exit using PLTPI or PLTSD The enabling and disabling processor is a CICS command-leel application module. After proper installation of this feature (see Installation considerations on page 24 and CICS table updates required on page 25), you can use the IBM-supplied PLTPI module KETXCPLN to automatically enable the IBM-supplied CICS SEND exit at CICS startup. Likewise you can use the same module KETXCPLN in the PLTSD to automatically disable the exit at CICS shutdown. Any confirmation or error messages from enabling and disabling are displayed as WTO messages on the master console. Refer to the IBM Tioli Monitoring and OMEGAMON Information Center at to search all OMEGAMON messages, or the IBM Tioli Monitoring: Messages book for explanations of ETE messages. Attention: This procedure just described is the preferred method for automatically enabling and disabling the CICS SEND exit. Enabling and disabling the exit using transaction KETX You can also use the CICS KETX transaction to directly enable or disable the CICS SEND exit or to iew the current status of the exit: KETX ENABLE Enables the CICS SEND exit. The abbreiation is KETX E. KETX DISABLE Disables the CICS SEND exit. The abbreiation is KETX D. KETX STATUS KETX DIAGNOSE Displays the current status of the CICS SEND exit. The abbreiation is KETX. Displays diagnostics if the CICS SEND exit is enabled. Use this transaction only if requested by IBM Software Support. The abbreiation is KETX DIAG. Confirmation or error messages from KETX display at the initiating terminal. Refer to the IBM Tioli Monitoring and OMEGAMON Information Center at index.jsp?toc=/com.ibm.itm.doc/toc.xml to search all OMEGAMON messages, or the IBM Tioli Monitoring: Messages book for explanations of ETE messages. 26 IBM Tioli OMEGAMON: ETE Reference