IBM Tioli OMEGAMON XE for CICS TG on z/os Version 5.1.0 User's Guide SC14-7476-00
IBM Tioli OMEGAMON XE for CICS TG on z/os Version 5.1.0 User's Guide SC14-7476-00
Note Before using this information and the product it supports, be sure to read the general information under Notices on page 51. This edition applies to ersion 5 release 1 modification 0 of IBM Tioli OMEGAMON XE for CICS on z/os (program number 5698-T07) and to all subsequent ersions, releases, and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the leel of the product. Copyright IBM Corporation 2009, 2012. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Tables..................................... Chapter 1. Introducing IBM Tioli OMEGAMON XE for CICS TG on z/os........... 1 OMEGAMON XE for CICS TG on z/os oeriew..................... 1 Using OMEGAMON XE for CICS TG on z/os...................... 2 New in this release................................ 2 Chapter 2. Predefined product workspaces...................... 3 Organization of the predefined workspaces....................... 3 Attribute groups used by the predefined workspaces.................... 4 CICSTG workspace................................ 4 Region Oeriew workspace............................. 5 CICS TS Region Details workspace.......................... 6 CICS TS Regions workspace............................ 7 Gateway Daemon Resources workspace........................ 7 Transaction Analysis workspace........................... 8 Actie Transactions workspace............................ 8 Transaction Flow Trace workspace.......................... 9 Response Time Analysis workspace......................... 10 End to End workspace.............................. 10 Chapter 3. Attributes............................... 13 CICSTG CICS TS Region Details attribute group..................... 14 CICSTG CICS TS Regions attribute group....................... 15 CICSTG Actie Transaction Analysis attribute group.................... 17 CICSTG Actie Transaction Details attribute group.................... 18 CICSTG Client Application Details attribute group..................... 21 CICSTG Connection Manager Threads attribute group................... 23 CICSTG Destination Serer Details attribute group.................... 24 CICSTG Gateway Daemon attribute group....................... 26 CICSTG Region Oeriew attribute group....................... 28 CICSTG Transaction Flow Trace attribute group..................... 30 CICSTG Transaction Response Time Details attribute group................. 32 CICSTG Transaction Response Time Summary attribute group................ 34 CICSTG Worker Threads attribute group........................ 36 Chapter 4. Situations............................... 37 Situation CICS TG CICS Communication Failure Warning................. 37 Situation CICS TG Connection Manager Thread Allocation Warning.............. 37 Situation CICS TG Connection Manager Threads Timeout Warning.............. 38 Situation CICS TG Connection Manager Threads Waiting Warning.............. 38 Situation CICS TG EXCI Pipe Allocation Failure Warning.................. 38 Situation CICS TG Freepipe Warning......................... 38 Situation CICS TG Health Critical.......................... 38 Situation CICS TG Health Warning.......................... 39 Situation CICS TG Rollback LUW Critical........................ 39 Situation CICS TG Rollback LUW Warning....................... 39 Situation CICS TG Rollback XA Critical........................ 39 Situation CICS TG Rollback XA Warning........................ 39 Situation CICS TG Status Warning.......................... 40 Situation CICS TG Worker Thread Allocation Warning................... 40 Situation CICS TG Worker Threads Timeout Warning................... 40 Copyright IBM Corp. 2009, 2012 iii
Appendix. Tioli Common Reporting........................ 41 Using Tioli Common Reporting........................... 41 Typical types of reports aailable with Tioli Common Reporting............... 42 OMEGAMON XE for CICS TG on z/os reports..................... 42 CICSTG Region Oeriew Performance........................ 43 Documentation library.............................. 45 OMEGAMON XE for CICS on z/os library....................... 45 OMEGAMON XE and Tioli Management Serices on z/os common library........... 45 IBM Tioli Monitoring publications.......................... 46 IBM CICS publication information centers....................... 47 Other sources of documentation........................... 47 Support information............................... 49 Notices.................................... 51 Trademarks.................................. 53 Index..................................... 55 i IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
Tables 1. The predefined workspaces and the attribute groups that populate them........... 4 2. CICSTG Region Oeriew Performance report.................... 43 Copyright IBM Corp. 2009, 2012
i IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
Chapter 1. Introducing IBM Tioli OMEGAMON XE for CICS TG on z/os IBM Tioli OMEGAMON XE for CICS TG on z/os (OMEGAMON XE for CICS TG on z/os) V5.1.0 is an optionally configured component in the runtime enironment of the IBM Tioli OMEGAMON XE for CICS on z/os base product. You can configure OMEGAMON XE for CICS TG on z/os in a runtime enironment without haing to configure OMEGAMON II for CICS or OMEGAMON XE for CICS on z/os. OMEGAMON XE for CICS TG on z/os offers a central point of management for CICS TG and CICS TG resource adapters deployed within the IBM WebSphere Application Serer on the z/os operating system. It comprehensiely gathers the information necessary to detect, correct, and preent problems within your CICS TG applications. Using the Tioli Enterprise Portal, you can iew the data gathered from the monitoring agent in tables and charts. These tables and charts indicate the status of your managed CICS TG address spaces (that is, instances of the CICS TG daemon), CICS TG connection factories in WebSphere Application Serer, and connectiity to CICS Transaction Serer. This information enables you to perform the following tasks: Collect and analyze reliable, up-to-the-minute data that allows you to make faster, better informed operating decisions Manage all CICS TG applications from a single point to identify problems at any time Track performance against goals Collect CICS TG statistics, which you can use to iew thread actiity, report CICS TS communication failures, examine resource waits and EXCI (External CICS Interface) pipe usage, and check for excessie transaction rollbacks, among other monitoring actiities Manage CICS TG actie transactions and proide response time analysis Monitor CICS TG resource adapters deployed within the WebSphere Application Serer. With OMEGAMON XE for CICS TG on z/os, systems administrators can set threshold leels and flags to alert them when system conditions reach these thresholds. They can use adanced monitoring facilities that include the following uses: User-defined and predefined situations based on thresholds to raise different types of alerts At-a-glance status of all CICS TG regions The capability to monitor multiple CICS TG regions simultaneously from one or more centralized workstations OMEGAMON XE for CICS TG on z/os oeriew CICS Transaction Gateway (CICS TG) is a high-performing, secure, and scalable connector that enables client applications in different runtime enironments to access CICS serers. Using standard-based interfaces, CICS TG deliers access to new and existing CICS applications using the following protocols: TCP/IP sockets Secure Sockets Layer (SSL) CICS TG proides a gateway to CICS for remote clients and complements IBM WebSphere Application Serer on seeral different platforms. In addition, it is designed to exploit the qualities of serice on the z/os platform, including high aailability and workload management. CICS TG proides a rich set of program interfaces that proide access to CICS COMMAREA, channel and 3270 applications. CICS TG proides APIs for Jaa,.NET, C/C++, COM, and COBOL. JCA resource adaptors and COM objects are also proided. Copyright IBM Corp. 2009, 2012 1
CICS TG can operate in either a two-tier or three-tier configuration. Each configuration proides different qualities of serice. The term "local mode" refers to the two-tier topology, while "remote mode" refers to the three-tier topology. In a local mode configuration, the CICS TG runs within the client application. Client applications send requests directly to CICS without using a Gateway daemon. In a remote mode configuration, the client application and CICS TG are on different machines and the Gateway daemon listens on a specific port for incoming client requests. The Gateway daemon runs as a standalone process, handles the management of connections and threads, and forwards client requests to CICS. Using OMEGAMON XE for CICS TG on z/os The OMEGAMON XE for CICS TG on z/os topics describe the arious pieces that make up the OMEGAMON XE for CICS TG on z/os monitor and the Tioli Enterprise Portal interface that lets you interact with the monitor. The sections in this book are diided into these topics, which correspond to the product's constituent pieces: Chapter 2, Predefined product workspaces, on page 3 Organization of the predefined workspaces on page 3 Attribute groups used by the predefined workspaces on page 4 Chapter 3, Attributes, on page 13 Chapter 4, Situations, on page 37 New in this release OMEGAMON XE for CICS TG on z/os proides full support for IBM Tioli Monitoring V6.2.3. In addition, V5.1.0 of this product incorporates new features and enhances existing functionality. The following sections proide details about these features: IBM Tioli Monitoring V6.2.3 support OMEGAMON XE for CICS TG on z/os V5.1.0 is designed to run on IBM Tioli Monitoring V6.2.3 and higher and proides support for many IBM Tioli Monitoring features. Read about these features in the IBM Tioli Monitoring User's Guide. OMEGAMON XE for CICS TG on z/os is an optionally configured component in the runtime enironment OMEGAMON XE for CICS TG on z/os is no longer a separately sold or installed product. The OMEGAMON XE for CICS TG on z/os configuration is now located under the CICS product selection menu in the Configuration Tool; this change also impacts the batch parameter configuration. You can configure the OMEGAMON XE for CICS TG on z/os component in your runtime enironment without configuring the OMEGAMON II for CICS or the OMEGAMON XE for CICS on z/os components. Configuration support to monitor CICS TG daemons through a secondary TCPIP stack on a local z/os operating system Use the Specify Nonstandard Parameters panel of the Configuration Tool to configure the INCLUDE statement with the bindaddress ariable to monitor CICS TG daemons through a secondary TCPIP stack on your local z/os operating system. 2 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
Chapter 2. Predefined product workspaces OMEGAMON XE for CICS TG on z/os proides predefined workspaces for iewing information about each managed CICS Transaction Gateway (CICS TG ) (that is, either Gateway daemons running in their own address space or connection factories defined with WebSphere Application Serer) you are monitoring. The table iews, graphs, and charts within each workspace report attribute information about each monitored CICS TG application. You can use them to perform the following tasks: Inestigate attribute information relating to a change in state. Monitor the performance of each CICS TG address space, helping you to identify system bottlenecks and ealuate tuning decisions. Identify the CICS Transaction Serer regions currently connected to CICS TG regions. Select the most effectie threshold alues for situations you create. Monitor transaction actiities from source to destination. Analyze transaction response times going in and out of CICS TG regions. Trace client application flows and organize indiidual requests into a single transaction. The workspaces delier detailed, current lifetime and static data that enable you to analyze CICS TG address spaces and applications. For an oeriew of aailable workspaces, see the next section, "Organization of the predefined workspaces." In addition to table iews and graphs, a workspace can contain other iews, for example, a 3270 terminal session, a text iew, a browser session, an eent console, or a Take Action pane that enables you to send commands to the operator console. Certain workspace iews proide links to subsidiary (that is, secondary) workspaces, as well as dynamic, runtime links to other OMEGAMON monitoring products, such as IBM Tioli OMEGAMON XE for CICS on z/os, IBM Tioli OMEGAMON XE on z/os, and IBM Tioli OMEGAMON XE for Mainframe Networks. Organization of the predefined workspaces OMEGAMON XE for CICS TG on z/os proides predefined workspaces that are displayed in the Naigator Physical iew. The following table is an alphabetical listing of these primary workspaces. Some workspaces are accessible only as links from other workspaces. These are called either secondary or subsidiary workspaces and are listed below their primary (that is, parent) workspace. For example, if you right-click either a row or the link icon in the CICS TS Regions workspace's Indiidual CICS Serer Summaries report and choose Link To, you can link (that is, transfer directly) to the CICS TS Region Details workspace on page 6. Actie Transactions workspace on page 8 Transaction Flow Trace workspace on page 9 CICSTG workspace on page 4 CICS TS Regions workspace on page 7 CICS TS Region Details workspace on page 6 End to End workspace on page 10 Gateway Daemon Resources workspace on page 7 Transaction Analysis workspace on page 8 Response Time Analysis workspace on page 10 For information about the attribute groups whose contents populate these workspaces, see Attribute groups used by the predefined workspaces on page 4. Copyright IBM Corp. 2009, 2012 3
Attribute groups used by the predefined workspaces In most cases, there is a one-to-one correspondence between a workspace and an attribute group; in other words, a workspace contains data or columns whose contents are extracted from the attributes in a single attribute group (although there is no such requirement it is certainly possible for a single workspace to be built from multiple attribute groups and for a single group's attributes to populate more than one workspace). Table 1 shows the relationships between the predefined workspaces and the attribute groups. The workspaces are listed in alphabetical order. Table 1. The predefined workspaces and the attribute groups that populate them Workspaces Related attribute groups Actie Transactions workspace on page 8 CICSTG Actie Transaction Details attribute group on page 18 CICSTG Actie Transaction Analysis attribute group on page 17 CICSTG workspace CICSTG Region Oeriew attribute group on page 28 CICS TS Region Details workspace on page 6 CICSTG CICS TS Region Details attribute group on page 14 CICS TS Regions workspace on page 7 CICSTG CICS TS Regions attribute group on page 15 CICSTG CICS TS Region Details attribute group on page 14 End to End workspace on page 10 CICSTG Client Application Details attribute group on page 21 CICSTG Destination Serer Details attribute group on page 24 Gateway Daemon Resources workspace on page 7 CICSTG Connection Manager Threads attribute group on page 23 CICSTG Worker Threads attribute group on page 36 Response Time Analysis workspace on page 10 CICSTG Transaction Response Time Details attribute group on page 32 CICSTG Transaction Response Time Summary attribute group on page 34 Transaction Analysis workspace on page 8 CICSTG Gateway Daemon attribute group on page 26 Transaction Flow Trace workspace on page 9 CICSTG Transaction Flow Trace attribute group on page 30 CICSTG workspace The predefined CICSTG workspace is the highest-leel workspace on the Tioli Enterprise Portal's tree iew for the IBM Tioli OMEGAMON XE for CICS TG on z/os monitor. This workspace proides an oeriew of the CICS TG region oeriews proided by the Region Oeriew workspace on page 5. When you select the CICSTG entry on the tree iew, it expands to a list of monitored CICS Transaction Gateway regions (these define the selectable Tioli Management Framework nodes). Note that a CICS TG region or address space can either be an instance of the CICS Transaction Gateway daemon or WebSphere Application Serer on z/os. The CICSTG workspace contains the following iews: The CPU Utilization bar chart shows the percentage of aailable CPU consumed by your site's CICS TG regions. 4 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
The Requests per Minute iew is a moing alue based on the number of requests since the last client interal expired. This ensures that the sample will be at least one interal long to preent sudden fluctuations when the counters are reset. The Requests per Minute iew is based on the statistics API data. The Gateway Daemon Oeriew table iew shows a row-by-row summary of each monitored CICS TG region currently running. From the Gateway Daemon Oeriew report, you can link dynamically to either the Tioli OMEGAMON XE for Mainframe Networks product or the Tioli OMEGAMON XE on z/os product, proided the target product is both installed and running when the link is inoked. Within the Tioli OMEGAMON XE for Mainframe Networks product, you can link to its Application Connections workspace, filtered on the System ID attribute. Within the Tioli OMEGAMON XE on z/os product, you can link to these workspaces, filtered on the System ID attribute: - Address Space Bottlenecks & Impact Analysis - Address Space CPU Usage Enclaes - Address Space Storage for Job - UNIX System Serices Processes Note: Statistical data is only aailable for Gateway daemon instances and is not aailable for WebSphere Application Serer regions. The CICSTG workspace is built from attributes in the CICSTG Region Oeriew attribute group on page 28. See also: CICSTG Region Oeriew attribute group on page 28 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Region Oeriew workspace The predefined region oeriew workspace proides detailed information about one of the CICS Transaction Gateway regions running in your site's z/os operating system enironment. When you select an OMEGAMON XE for CICS TG on z/os region from the Naigator Physical iew, the Naigator Physical iew entry expands to list the arious primary workspaces it defines, and the region oeriew workspace itself opens. Note that a CICS TG region or address space may either be an instance of the CICS TG daemon or WebSphere Application Serer on z/os. In a Gateway daemon instance, the workspace name takes the form <ctgname>:<smfid>:cicstg, where ctgname is the eight character CICS TG region name and smfid is the four character z/os system identifier. In a WebSphere Application Serer instance, the identifier is <ctgname>:<smfid>:cicstg-was. This workspace contains the following iews: The Requests graph shows the number of requests ersus time for this Gateway daemon. The Requests per Minute iew is a moing alue based on the number of requests since the last client interal expired; this ensures that the sample is at least one interal long to preent sudden fluctuations when the counters are reset. The Requests per Minute iew is based on the statistics API data. The Gateway Daemon Oeriew for <ctgname> table iew shows detailed information about the current CICS TG region. From the Gateway Daemon Oeriew for <ctgname> report, you can link dynamically to either the Tioli OMEGAMON XE for Mainframe Networks product or the Tioli OMEGAMON XE on z/os product, proided the target product is both installed and running when the link is inoked. Within the Tioli OMEGAMON XE for Mainframe Networks product, you can link to the Application Connections workspace, filtered on the System ID attribute. Chapter 2. Predefined product workspaces 5
Within the Tioli OMEGAMON XE on z/os product, you can link to these workspaces, filtered on the System ID attribute: - Address Space Bottlenecks & Impact Analysis - Address Space CPU Usage Enclaes - Address Space Storage for Job - UNIX System Serices Processes The region oeriew workspace is built from attributes in the CICSTG Region Oeriew attribute group on page 28. See also: CICSTG Region Oeriew attribute group on page 28 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 CICS TS Region Details workspace The predefined CICS TS Region Details secondary workspace proides a detailed look at a single CICS Transaction Serer accessed by applications running in the selected CICS TG daemon. The CICS TS Region Details workspace is reached using a link from the Indiidual CICS Region Summaries table iew in the CICS TS Regions workspace on page 7. This workspace contains these iews: The Percentage of Requests Executed and Pipes Allocated for <regionname> bar chart shows the percentages of CICS TG requests executed by and EXCI pipes allocated for this CICS TS region. The CICS TS Region Details table iew proides detailed information about the selected CICS TS region. From the CICS TS Region Details graph, you can link dynamically to any of the following workspaces within the OMEGAMON XE for CICS on z/os product, if this product is both installed and running at your site when the link is inoked. This link is filtered on the System ID and CICS TS Region Jobname attributes: Bottleneck Analysis Connections Analysis Region Oeriew Transaction Analysis Transaction Manager Statistics UOW Enqueue Analysis The Pipe Allocation Failures and Request Executions per Minute for <regionname> table iew shows both the number of pipe allocation failures and the number of requests executed for the selected CICS TG. The CICS TS Region Details workspace is built from the attributes in the CICSTG CICS TS Region Details attribute group on page 14. Note: This workspace is only aailable if you are iewing a Gateway daemon region. This workspace is not displayed if you are iewing a CICS TG running locally under a WebSphere serer. See also: CICSTG CICS TS Region Details attribute group on page 14 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 6 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
CICS TS Regions workspace The predefined CICS TS Regions primary workspace proides an oeriew of the arious CICS Transaction Serer regions that hae been accessed, successfully or unsuccessfully, by the selected CICS Transaction Gateway daemon. This workspace contains these iews: The Indiidual CICS TS Regions bar chart shows the percentage of EXCI pipes allocated and the percentage of requests executed for each CICS Transaction Serer region accessed by this CICS TG. The CICS Regions Summary table proides summary information about all the CICS TS regions accessed by this CICS TG; this includes all CICS TS regions to which a client's work request has been sent while this Gateway daemon has been actie. The Indiidual CICS Region Summaries table iew shows detailed information about each CICS TS region accessed by this CICS TG. This report includes CICS TS regions for which it has been unsuccessful in making requests for whateer reason. From the Indiidual CICS Region Summaries table, you can link to the CICS TS Region Details workspace on page 6, to retriee detailed statistical information about an indiidual CICS Transaction Serer region. You can also link dynamically to any of the following workspaces within the OMEGAMON XE for CICS on z/os product, if it is both installed and running at your site when the link is inoked. This link is filtered on the System ID and CICS TS Region Jobname attributes: Bottleneck Analysis Connections Analysis Region Oeriew Transaction Analysis Transaction Manager Statistics UOW Enqueue Analysis The CICS TS Regions workspace is built from attributes proided by the CICSTG CICS TS Regions attribute group on page 15 and the CICSTG CICS TS Region Details attribute group on page 14. Note: This workspace is only aailable if you are iewing a Gateway daemon region. This workspace is not displayed if you are iewing a CICS TG running locally under a WebSphere serer. See also: CICSTG CICS TS Regions attribute group on page 15 CICSTG CICS TS Region Details attribute group on page 14 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Gateway Daemon Resources workspace The Gateway Daemon Resources workspace proides detailed information about the arious threads running in the selected CICS TG daemon. This workspace contains these iews: The Connection Manager Threads Allocated bar chart shows statistics regarding the status of Connection Manager threads within the selected CICS TG. This includes the number of threads created and aailable within the thread pool, the number currently allocated to a connected client application, and the number of allocated threads that are waiting for a Worker thread to become aailable. The Worker Threads Allocated bar chart shows statistics regarding the status of Worker threads within the selected CICS TG. This includes the number of threads created and aailable within the thread pool and the number currently allocated to a connected client application allowing a work request to be flowed through to CICS. Chapter 2. Predefined product workspaces 7
The Connection Manager Threads Summary table iew proides detailed information about the current CICS TG's allocation and use of Connection Manager threads. The Worker Threads Summary table iew proides detailed information about the selected CICS TG's allocation and use of Worker threads. The Gateway Daemon Resources workspace is built from attributes proided by the CICSTG Connection Manager Threads attribute group on page 23 and the CICSTG Worker Threads attribute group on page 36. Note: This workspace is only aailable if you are iewing a Gateway daemon region. This workspace is not displayed if you are iewing a CICS TG running locally under a WebSphere serer. See also: CICSTG Connection Manager Threads attribute group on page 23 CICSTG Worker Threads attribute group on page 36 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Transaction Analysis workspace The Transaction Analysis workspace proides a detailed look at the arious CICS transactions types (XA, Extended LUW, and SYNCONRETURN) that can be inoked by a connected client application through the CICS Transaction Gateway region. This workspace contains these iews: The Ratio of Transaction Types bar chart shows all the CICS transactions currently being processed by this CICS TG daemon, broken down by transaction type (XA transactions ersus Extended LUW transactions ersus SYNCONRETURN transactions). The Gateway Daemon Summary table shows detailed information about the types of transactions being processed by this CICS TG daemon, broken down by type (XA transactions, extended LUW transactions, SYNCONRETURN transactions). For XA and Extended LUW transactions, the number of transactions committed and rolled-back are proided. The Extended LUW Transactions Ratio bar chart compares the number of extended LUW transactions that were committed to those that had to be rolled back. The XA Transactions Ratio bar chart compares the number of XA transactions that were committed to those that had to be rolled back. The Transaction Analysis workspace is built from the attributes in the CICSTG Gateway Daemon attribute group on page 26. Note: This workspace is only aailable if you are connected to a CICS TG region. This workspace is not displayed if you are connected to a WebSphere serer. See also: CICSTG Gateway Daemon attribute group on page 26 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Actie Transactions workspace The Actie Transactions workspace shows an oeriew of all actie transactions running through a CICS TG daemon or WebSphere Application Serer at the gien sampling time. It proides an impression of how the Gateway is performing and gies detailed transaction information. Though the workspace only shows a snapshot of actie transactions near completion, blocked transactions or transactions in waiting are much more easily identified. This workspace contains three iews: 8 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
The Actie Transaction Details table shows the indiidual transactions currently running on the selected CICS TG region. Selecting a transaction links you to the Transaction Flow Trace workspace. The Aerage Transaction Elapsed Time bar chart shows aerage elapsed time across all transactions along with the longest and shortest running time for actie transactions. The Aerage Transaction Payload and Wiresize bar chart shows the aerage payload and wiresize across all transactions flowed through the selected CICS TG. Notes: 1. Data is only present in this workspace, if transaction monitoring has been configured for this CICS TG. 2. If and when a transaction in CICS TG is hung, according to the data on this workspace, it is likely that no response has been receied from the CICS Transaction Serer; CICS TG purged the transaction. Howeer, the OMEGAMON Monitoring Exit was not informed in order to record the end of the transaction because that exit in the CICS TG region was not inoked for that specific transaction. The transaction is cleared from this workspace once CICS TG is recycled. The Actie Transactions workspace is built from the attributes in the CICSTG Actie Transaction Details attribute group on page 18 and CICSTG Actie Transaction Analysis attribute group on page 17. See also: CICSTG Actie Transaction Details attribute group on page 18 CICSTG Actie Transaction Analysis attribute group on page 17 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Transaction Flow Trace workspace This workspace is a secondary workspace reached by a link in the Actie Transactions Details table of the Actie Transactions workspace on page 8. This workspace breaks down a specific transaction into indiidual flows. It is a multi-row table that contains one row per flow displayed by the order in which it was recorded, normally in chronological order. This workspace should be isited once you hae already identified a particular transaction of interest; it shows whether a problem is still occurring or if the problem has already been resoled. This workspace contains four iews: The Actie Transaction Details table is a single-row table that contains the data from the linked table in the Actie Transactions workspace on page 8. The Elapsed Time Per Flow bar chart shows the total trip time or flow duration for completed flows or the elapsed time of a currently actie flow, if any. The Payload and Wiresize Per Flow bar chart shows the payload and wiresize of each flow either to or from CICS that makes up a composite part of this transaction. The Transaction Flow Trace table is a multi-row table where each row represents a completed flow either to or from CICS that makes up a composite part of this transaction. The Transaction Flow Trace workspace is built from the attributes in the CICSTG Transaction Flow Trace attribute group on page 30. See also: CICSTG Transaction Flow Trace attribute group on page 30 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Chapter 2. Predefined product workspaces 9
Response Time Analysis workspace The Response Time Analysis workspace shows durations for both the request and response flows of completed transactions as they pass through a CICS TG daemon or WebSphere Application Serer. The information is based on completed transactions and shows the time spent in the Gateway by the requests and responses. This workspace also displays the time in between the request leaing the Gateway and a response being receied. This workspace contains three iews: The Aerage Transaction Payload and Wiresize bar chart shows the aerage transaction payload and aerage transaction wiresize. The Completed Transaction Response Time bar chart displays the aerage request duration, aerage transaction duration outside CICS TG, aerage response duration, and the aerage time waiting for the Worker. The graph also shows the ratio of these times as well as a isual indication of where any delay is occurring. The Transactions Response Time Details multi-row table Note: Data is only present in this workspace if transaction monitoring has been configured for this CICS TG. The Response Time Analysis workspace is built from the attributes in the CICSTG Transaction Response Time Details attribute group on page 32 and CICSTG Transaction Response Time Summary attribute group on page 34. See also: CICSTG Transaction Response Time Summary attribute group on page 34 CICSTG Transaction Response Time Details attribute group on page 32 Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 End to End workspace The End to End workspace gies quantitatie analysis from both the source Client applications (where work originates) and the workload sent to destination CICS Transaction Serer regions (where work is processed). This workspace is aailable for iewing both CICS TG daemon and WebSphere Application Serer regions. This workspace contains six iews: The Client Application Details table. The Destination Serer Details table. The Payload and Wiresize per Client Application bar chart displays quantitatie information about the Payload and Wiresize organized by IP address. The Payload and Wiresize per Destination Serer bar chart displays quantitatie information about the Payload and Wiresize organized by CICS region. The Response Times Per Client Application bar chart shows the Inbound Requests Per Minute organized by IP address and may identify bottlenecks. The Response Times Per Destination Serer bar chart shows the Onbound Requests Per Minute organized by CICS Region and may identify bottlenecks. Note: Data is only present in this workspace if transaction monitoring has been configured for this CICS TG. The End to End workspace is built from the attributes in the CICSTG Client Application Details attribute group on page 21 and the CICSTG Destination Serer Details attribute group on page 24. See also: CICSTG Client Application Details attribute group on page 21 CICSTG Destination Serer Details attribute group on page 24 10 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
Attribute groups used by the predefined workspaces on page 4 Organization of the predefined workspaces on page 3 Chapter 2. Predefined product workspaces 11
12 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
Chapter 3. Attributes Tioli Enterprise Portal gathers data from remote agents running on the same z/os operating systems where WebSphere Application Serers or CICS Transaction Gateway daemons run. It stores this data for OMEGAMON XE for CICS TG on z/os in elements called attributes. Each attribute is a characteristic of an object. For example, CICS Transaction Gateway Name is an attribute that identifies a specific CICS Transaction Gateway region. Attribute groups OMEGAMON XE for CICS TG on z/os attributes are grouped into numerous attribute groups of related items. For example, the attributes in the Gateway Daemon group gather information about the arious transactions being inoked by the applications using a particular CICS TG daemon. These attributes correspond to the column names in the table iews and the items in the arious graphic displays for bar charts and so forth. Attributes and workspaces You can iew the data reported for the attributes in the tables and charts displayed in the OMEGAMON XE for CICS TG on z/os workspaces. This data enables you to: Manage all CICS TG regions from a single point to identify problems at any time Track performance against goals For an understanding of how indiidual attribute groups relate to the OMEGAMON XE for CICS TG on z/os workspaces, see Attribute groups used by the predefined workspaces on page 4. Attributes and situations Various attributes are used in the product's predefined situations. You can also reference the OMEGAMON XE for CICS TG on z/os attributes in your own situations to monitor the performance of a single CICS Transaction Gateway region or multiple regions. These situations can monitor one aspect of your enterprise or analyze multiple conditions to alert you to problems and their causes. Note: Certain attribute groups are not aailable for use in situations; these are not listed when you inoke the situation editor. Copyright IBM Corp. 2009, 2012 13
CICSTG CICS TS Region Details attribute group The CICSTG CICS TS Region Details attribute group reports detailed information about a selected CICS Transaction Serer region that has been the target of at least one work request from this CICS Transaction Gateway daemon. These attributes populate both the CICS TS Regions workspace on page 7 and the CICS TS Region Details workspace on page 6. CICS TS Region Applid Is the APPLID for the selected CICS TS region. An alphanumeric string, maximum eight characters. CICS TS Region Jobname Is the jobname assigned to the CICS TS region. An alphanumeric string, maximum eight characters. EXCI Pipe Allocate Failures Is the number of times the Gateway daemon has tried and failed to allocate a pipe to the selected CICS TS region. A EXCI Pipe Allocation Failures Per Minute Is the number of times the Gateway daemon has tried and failed to allocate a pipe to this CICS TS region oer the most recent sampling interal, diided by the duration of the interal (from 60 to 120 seconds) to gie the aerage oer the past minute. A nonnegatie integer. EXCI Pipes Allocated Is the current number of EXCI pipes allocated to worker threads to send and receie data for the selected CICS TS region. A Gateway Daemon Name Indicates the jobname of the address space running the CICS TG daemon being monitored. An alphanumeric string, maximum eight characters. Origin Node Is the combination of the CICS TG jobname, the z/os System ID (SMFID), and the CICSTG string. An alphanumeric string, maximum 32 bytes and case-sensitie, format <jobname>:<smfid>:cicstg. When a situation is true, the system compares the origin node name in the attribute to the names of managed systems assigned to the situation. If the origin node name matches the name of a managed system, the node's status changes accordingly. If the names of the origin node and the managed systems do not match, the status remains unchanged. Percentage Of Pipes Allocated Is the percentage of pipes allocated to the selected CICS TS region relatie to all CICS TS regions. A Percentage Of Requests Executed Is the percentage of EXCI requests that hae been processed (successful and failed) by the selected CICS TS region relatie to all CICS TS regions. A nonnegatie integer. Requests Executed Is the number of EXCI requests that hae been processed (successful and failed) for the selected CICS TS region. A Requests Executed Per Minute Is the number of EXCI requests that hae been processed (successful and failed) for the selected CICS TS region oer the most recent sampling interal, diided by the duration of the interal (from 60 to 120 seconds) to gie the aerage oer the past minute. A System ID Is the four character name that identifies the z/os System ID (SMFID) that is hosting this CICS TG daemon. An alphanumeric string, maximum four characters. z/os System IDs are always in uppercase characters. 14 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
CICSTG CICS TS Regions attribute group The CICSTG CICS TS Regions attribute group reports information about all the CICS TS regions your Gateway daemon has either connected to or attempted to connect to during its lifetime. These attributes populate the CICS TS Regions workspace on page 7. Communication Failures Is the number of times the Gateway daemon failed to connect to a CICS TS region een though a pipe was aailable. A Communication Failures Per Minute Is the rate at which the Gateway daemon failed to connect to a CICS TS region een though a pipe was aailable oer the most recent sampling interal, diided by the duration of the interal (from 60 to 120 seconds) to gie the aerage oer the past minute. A nonnegatie integer. CICS TS Region Count Is the number of CICS TS regions, defined by APPLID, to which the Gateway daemon has tried to send at least one request during its lifetime. This number can increase but neer decreases. A EXCI NETNAME Is the NETNAME of the specific pipe used for EXCI calls (the empty string if generic pipes are being used). This alue is defined by the enironment ariable DFHJVPIPE. An alphanumeric string, maximum eight characters. EXCI Pipe Allocation Failures Is the number of times the Gateway daemon tried and failed to allocate a pipe to a CICS TS region. A EXCI Pipe Allocation Failures Per Minute Is the rate at which the Gateway daemon tried and failed to allocate a pipe to a CICS TS region oer the most recent sampling interal, diided by the duration of the interal (from 60 to 120 seconds) to gie the aerage oer the past minute. A EXCI Pipe Limit Is the EXCI pipe allocation limit for each z/os address space (equialent to system initialization parameter LOGONLIM). A EXCI Pipe Reallocations Is the number of times a Worker thread had to deallocate its existing pipe and reallocate a new pipe because the existing pipe points to a different CICS TS region from that identified by the request. Cases where the worker thread's pipe was deallocated and reallocated because the CICS TS region was not aailable are excluded. This statistic applies only when the pipe reuse model is set to one reuse per thread. A EXCI Pipes Allocated Is the number of currently allocated EXCI pipes across all CICS TS regions. A Free Pipes Is the current number of aailable EXCI pipes across all CICS regions. A Gateway Daemon Name Indicates the jobname of the address space running the CICS TG daemon being monitored. An alphanumeric string, maximum eight characters. Origin Node Is the combination of the CICS TG jobname, the z/os System ID (SMFID), and the CICSTG string. An alphanumeric string, maximum 32 bytes and case-sensitie, format <jobname>:<smfid>:cicstg. When a situation is true, the system compares the origin node name in the attribute to the names of managed systems assigned to the situation. If the origin node name matches the name of a managed system, the node's status changes accordingly. If the names of the origin node and the managed systems do not match, the status remains unchanged. Chapter 3. Attributes 15
Requests Executed Is the number of EXCI requests that hae been processed (successful and failed) across all CICS TS regions. A Requests Executed Per Minute Is the number of EXCI requests that hae been processed (successful and failed) for all CICS TS regions oer the most recent sampling interal, diided by the duration of the interal (from 60 to 120 seconds) to gie the aerage oer the past minute. A System ID Is the four character name that identifies the z/os System ID (SMFID) that is hosting this CICS TG daemon. An alphanumeric string, maximum four characters. z/os System IDs are always in uppercase characters. 16 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
CICSTG Actie Transaction Analysis attribute group The Actie Transaction Details attribute group proides totals for actie transactions, failure count, aerage running time, payload, and wiresize. These attributes populate the Actie Transactions workspace on page 8. Aerage Elapsed Time Is the aerage elapsed time of actie transactions in milliseconds. A nonnegatie integer. Aerage Payload Is the aerage size of COMMAREA receied from or about to be sent to CICS TS. A Aerage Wiresize Is the aerage number of bytes of data receied from or about to be sent to the Client. A CICS Transaction Gateway Name Indicates the jobname of the CICS Transaction Gateway daemon for the region that is being monitored. An alphanumeric string, with a maximum of eight characters. Failed Transactions Is the number of failed transactions. A Maximum Elapsed Time Is the elapsed time of the slowest transaction. A Maximum Payload Is the largest size of COMMAREA receied from or about to be sent to CICS TS. A Maximum Wiresize Is the largest number of bytes of data receied from or about to be sent to the Client. A Minimum Elapsed Time Is the elapsed time of the most recent actie transaction in milliseconds. A Minimum Payload Is the smallest size of COMMAREA receied from or about to be sent to CICS TS. A Minimum Wiresize Is the smallest number of bytes of data receied from or about to be sent to the Client. A Number of Actie Transactions Is the number of currently actie transactions. A Origin Node Is the combination of the CICS TG jobname, the z/os System ID (SMFID), and the CICSTG string. An alphanumeric string, maximum 32 bytes and case-sensitie, format <jobname>:<smfid>:cicstg. When a situation is true, the system compares the origin node name in the attribute to the names of managed systems assigned to the situation. If the origin node name matches the name of a managed system, the node's status changes accordingly. If the names of the origin node and the managed systems do not match, the status remains unchanged. System ID Is the four character name that identifies the z/os System ID, (SMFID) that is hosting this CICS TG daemon. An alphanumeric string, maximum four characters. z/os System IDs are always in uppercase characters. Chapter 3. Attributes 17
CICSTG Actie Transaction Details attribute group The Actie Transaction Details attribute group proides detailed information for all actie transactions. A single transaction is made of multiple flows which are started by the Client application or by CICS TG on behalf of a Client Application. These attributes populate the Actie Transactions workspace on page 8. CICS TG Abend Code Is the last CICS TS Abend code reported for this transaction. An alphanumeric string, maximum four characters. CICS TG Applid Is the CICS TG Applid as specified in the PRODUCT section of the Gateway daemon configuration file (ini). An alphanumeric string, maximum eight characters. CICS TG Applid High Leel Qualifier Is the CICS TG Applid high leel qualifier as specified in the PRODUCT section of the Gateway daemon configuration file (ini). An alphanumeric string, maximum eight characters. CICS TG Correlator Is the CICS TG correlator used for transaction tracking. A CICS TG Return Code Is the last CICS TG return code reported for this transaction. A nonnegatie integer. CICS TS Abend Code Is the last CICS TS Abend code reported for this transaction. An alphanumeric string, maximum four characters. CICS TS Return Code Is the last CICS TS return code reported for this transaction. A nonnegatie integer. CICS Transaction Gateway Name Indicates the jobname of the CICS Transaction Gateway daemon for the region that is being monitored. An alphanumeric string, with a maximum of eight characters. Client CICS TG Applid Is the CICS TG of the Client classes calling the Gateway daemon classes. An alphanumeric string, maximum eight characters. Client CICS TG Applid High Leel Qualifier Is the CICS TG Applid high leel qualifier of the Client classes calling the Gateway daemon classes. An alphanumeric string, maximum eight characters. Client CICS TG Correlator Is the CICS TG correlator of the Client classes calling the Gateway daemon classes used for transaction tracking. A Client Location Is the IP address or the source Client application. An alphanumeric string, maximum 45 characters. Gateway Location Is the IP address or the location of this Gateway daemon. An alphanumeric string, maximum 45 characters. Gateway URL Is the first 128 bytes of the URL of the Gateway daemon. An alphanumeric string, maximum 128 characters. Method Is the communication method, either EXCI or IPIC. Origin Node Is the combination of the CICS TG jobname, the z/os System ID (SMFID), and the CICSTG string. An alphanumeric string, maximum 32 bytes and case-sensitie, format <jobname>:<smfid>:cicstg. 18 IBM Tioli OMEGAMON XE for CICS TG on z/os: User's Guide
When a situation is true, the system compares the origin node name in the attribute to the names of managed systems assigned to the situation. If the origin node name matches the name of a managed system, the node's status changes accordingly. If the names of the origin node and the managed systems do not match, the status remains unchanged. Number Of Flows Is the total number of flows in this transaction. A Payload Is the total size of the COMMAREA receied from or about to be sent to the Client. A Program Name Is the program name in the CICS TS. An alphanumeric string, maximum eight characters. Request Arrial Time Is the time that the first request arried in CICS TG. The alid format is a 16-character timestamp. Request Departure Time Is the time that the latest request left CICS TG for CICS TS. The alid format is a 16-character timestamp. Request Duration In CICS TG Is the time spent in CICS TG before requests were to CICS TS. A Response Arrial Time Is the time that the latest response arried in CICS TG from CICS TS. The alid format is a 16-character timestamp. Response Departure Time Is the time that the latest response left CICS TG. The alid format is a 16-character timestamp. Response Duration In CICS TG Is the time spent in CICS TG after responses were receied from CICS TS. A Serer Name Is the name of the CICS TS where the transaction was processed. This may not be the CICS TS jobname or APPLID. An alphanumeric string, maximum eight characters. Status Indicates whether or not the actie transaction failed. System ID Is the four character name that identifies the z/os System ID (SMFID) that is hosting this CICS TG daemon. An alphanumeric string, maximum four characters. z/os System IDs are always in uppercase characters. Time Waiting For Worker Is the time the CICS TG had to wait for a Worker thread. A nonnegatie integer. Topology Is the flow topology type of either Gateway, RemoteClient, or LocalClient. Transaction Duration Outside CICS TG Is the time spent outside of CICS TG and includes the time spent in CICS TS and the network, if not EXCI. A Transaction Elapsed Time Is the elapsed time or duration of the transaction. A Transaction ID Is the transaction ID in CICS TS. An alphanumeric string, maximum four characters. Type Is the Transaction type of either Synconreturn, ExtendedMode, or XA. User ID Is the user ID associated with this transaction. An alphanumeric string, maximum eight characters. Chapter 3. Attributes 19