Main r3

Tivoli Monitoring for Applications: mySAP Agent
Version 6.1.0
Users Guide
SC32-9443-00
Tivoli Monitoring for Applications: mySAP Agent
Version 6.1.0
Users Guide
SC32-9443-00
Note Before using this information and the product it supports, read the information in Appendix E, Notices, on page 247.
First Edition (May 2006) This edition applies to version 6.1 of IBM Tivoli Monitoring for Applications: mySAP Agent (product number 5724-B97) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . vii About this guide . . . . . . . . . . . ix
Who should read this guide . . . . . . . . . ix What this guide contains . . . . . . . . . . ix Publications . . . . . . . . . . . . . . x Prerequisite publications . . . . . . . . . x Related publications . . . . . . . . . . xi Accessing terminology online . . . . . . . xi Accessing publications online . . . . . . . xi Ordering publications . . . . . . . . . . xi Accessibility . . . . . . . . . . . . . . xii Tivoli technical training . . . . . . . . . . xii Support information . . . . . . . . . . . xii Conventions used in this guide . . . . . . . . xii Typeface conventions . . . . . . . . . . xii Operating system-dependent variables and paths . . . . . . . . . . . . . . . xiii mySAP RFC connections . . . . . . . . . Optional advanced configuration in mySAP . . Centralized CCMS reporting . . . . . . . . Non-Unicode double-byte language support . . Removing remote function modules from mySAP 21 21 23 24 25
Chapter 3. How to use the Monitoring Agent for mySAP . . . . . . . . . . 27

View real-time data about mySAP . . . Investigate an event . . . . . . . Recover the operation of a resource . . Customize your monitoring environment Monitor with custom situations that meet requirements . . . . . . . . . . Collect and view historical data . . . . . . . . . . . your . . . . . . . . . . . . . . 27 28 28 29
. 30 . 31
Chapter 4. Workspaces reference . . . 33

About workspaces . . . . . . . . . . Monitoring Agent for mySAP Navigator tree Predefined launch definitions . . . . . Action links . . . . . . . . . . . Time spans . . . . . . . . . . . More information about workspaces . . . . Predefined workspaces . . . . . . . . ABAP Dumps workspace . . . . . . . Active Users workspace . . . . . . . Alerts workspace . . . . . . . . . Application Performance workspace . . . Archive Monitor workspace . . . . . . Asynchronous Updates workspace . . . Batch Data Create Log workspace . . . . Batch Data Create workspace . . . . . Batch Job Log workspace . . . . . . . Batch Jobs workspace . . . . . . . . Buffer Performance workspace . . . . . Close Alert Results workspace . . . . . Close All Alerts Results workspace . . . Database workspace . . . . . . . . Data Transfer Information workspace . . . Database Logs workspace . . . . . . Developer Traces workspace . . . . . . Disable Gateway Statistics Results workspace Enable Gateway Statistics Results workspace Enqueue Locks workspace . . . . . . File Systems workspace . . . . . . . Gateway Statistics workspace . . . . . Historical Database workspace . . . . . Historical Operating System workspace . . Historical Service Response Time workspace Instance Configuration . . . . . . . Instance Summary workspace . . . . . Logon Groups workspace . . . . . . Logon Information workspace . . . . . Memory workspace. . . . . . . . . Number Range Buffer workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 33 33 34 34 34 35 36 37 38 41 41 42 42 42 43 43 44 45 45 45 46 46 47 47 47 48 48 48 49 49 49 49 50 50 50 51 51
Chapter 1. Overview of the Monitoring Agent for mySAP . . . . . . . . . . . 1

IBM Tivoli Monitoring overview . . . . . Features of Monitoring Agent for mySAP . . Components of Monitoring Agent for mySAP User interface options . . . . . . . . . . . . . . . . . . . . 1 1 2 3
Chapter 2. Requirements and configuration for the monitoring agent . 5

Requirements for the monitoring agent . . . . . 5 Basic installation and configuration of the Monitoring Agent for mySAP . . . . . . . . . . . . . 6 Installing to the mySAP system . . . . . . . 7 Installing to the IBM Tivoli Monitoring system 10 Configuring the Monitoring Agent for mySAP . . 10 Starting or stopping the Monitoring Agent for mySAP . . . . . . . . . . . . . . . 13 Remote deployment . . . . . . . . . . . 14 Deploying the monitoring agent remotely from the Tivoli Enterprise Portal . . . . . . . . 14 Deploying the monitoring agent using the tacmd command . . . . . . . . . . . . . . 15 Advanced installation and configuration of the Monitoring Agent for mySAP . . . . . . . . 15 Remote management . . . . . . . . . . 16 mySAP user IDs . . . . . . . . . . . . 16 Using ksar3 and ksar3exe to run automated functions . . . . . . . . . . . . . . 18 Using ksanfy and ksar3nfy to send SAP Office email . . . . . . . . . . . . . . . 18 Environment variables in ksar3 and ksanfy script files . . . . . . . . . . . . . . . . 18 Using ksapwd and ksar3pwd to encrypt a password . . . . . . . . . . . . . . 19 sapshcut command . . . . . . . . . . . 20
Copyright IBM Corp. 2006
iii
Operating System and LAN workspace . . Output Requests workspace . . . . . . Refresh Database Statistics Results workspace Reset Gateway Statistics Results workspace . SAP Office Inbox workspace . . . . . . SAProuter Log workspace . . . . . . Service Response Time workspace . . . . Spool Output workspace . . . . . . . Spool Requests workspace . . . . . . Sub-Application Performance workspace . System Log Detail workspace . . . . . System Log workspace . . . . . . . System Summary (agent level) workspace . System Summary (system level) workspace . Transaction Performance workspace . . . Transactional RFC workspace . . . . . Transport Log workspace . . . . . . . Transport Objects and Steps workspace . . Transport Requests workspace . . . . . User Information workspace . . . . . . User Performance workspace . . . . . User Transaction Performance workspace . Work Processes workspace . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
51 52 52 53 53 53 54 54 54 55 55 55 56 56 56 57 57 58 58 59 59 60 60
System Log Details attributes . . . Topology Information attributes . . Transaction Performance attributes . Transactional RFC attributes . . . Transport Log attributes . . . . . Transport Objects attributes . . . Transport Requests attributes . . . Transport Steps attributes . . . . Updates Information attributes . . User Information attributes . . . . Work Processes attributes . . . . Disk capacity planning for historical data
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
116 117 117 120 122 122 123 125 127 128 130 134
Chapter 6. Situations reference . . . . 141

About situations . . . . . . . More information about situations . Predefined situations . . . . . . ABAP Dump situations . . . . Active Users situations . . . . Alert situations . . . . . . . Batch Data Create situations . . Batch Jobs situations . . . . . Buffer situations . . . . . . Database situations . . . . . Delete Product-provided situations Dialog situations . . . . . . Excess Memory situation . . . File Systems situations . . . . Gateway Connections situation . Instance Configuration situations . Locks situations . . . . . . Login and Logoff situations . . Number Range situation. . . . OS and LAN situations . . . . Output situations . . . . . . Private Memory situation . . . Private Mode situation . . . . Response Time situations . . . SAPGUI situations . . . . . SAP Office situation . . . . . SAP Router situation . . . . . Service Response situations . . . Spool situations . . . . . . System Log situations . . . . Transactional RFC situation. . . Transport situations . . . . . Updates situations . . . . . . Work Processes situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 141 142 145 145 146 146 146 147 149 150 150 150 150 151 151 152 152 152 152 153 154 154 154 154 154 154 154 156 156 157 157 157 158
Chapter 5. Attributes reference . . . . 63

About attributes . . . . . . . . . . . More information about attributes . . . . . Attribute groups and attributes . . . . . . ABAP Dumps attributes . . . . . . . Active Users attributes . . . . . . . Alerts attributes . . . . . . . . . . Archive Monitor attributes . . . . . . Batch Data Create attributes . . . . . . Batch Data Create Log attributes . . . . Batch Jobs attributes . . . . . . . . Batch Job Logs attributes . . . . . . . Buffer Performance attributes . . . . . Data Base Detail attributes . . . . . . Data Base Summary attributes . . . . . Database Logs attributes . . . . . . . Developer Traces attributes . . . . . . EDI Files attributes . . . . . . . . . File Systems attributes . . . . . . . . Gateway Connections attributes . . . . Gateway Statistics attributes . . . . . . Instance Configuration attributes . . . . Intermediate Documents attributes . . . Lock Entries attributes . . . . . . . . Logon Group attributes . . . . . . . Logon Information attributes . . . . . Number Range Buffer Details attributes . Number Range Buffer Summary attributes Operating System Performance attributes . Output Requests attributes . . . . . . Perform Requested Action attributes. . . SAP Office Inbox attributes . . . . . . Saprouter Log attributes . . . . . . . Service Response Time attributes . . . . Set Default Sample Period attributes . . . Spool Requests attributes . . . . . . System Log attributes. . . . . . . . . 63 . 63 . 64 . 65 . 66 . 67 . 69 . 71 . 72 . 73 . 75 . 76 . 79 . 80 . 82 . 82 . 83 . 84 . 85 . 87 . 91 . 95 . 97 . 98 . . 100 . . 101 . . 102 . . 104 . . 105 . . 108 . . 108 . . 110 . . 111 . . 113 . . 113 . . 115 . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7. Take Action commands reference . . . . . . . . . . . . . 159

About Take Action commands . . . . . . . More information about Take Action commands Predefined Take Action commands . . . . . Cancel Job action . . . . . . . . . . Close Alert action . . . . . . . . . . Delete Job action . . . . . . . . . . Execute brarchive action . . . . . . . . Output Request action . . . . . . . . Start Job action . . . . . . . . . . . . 159 159 . 159 . 160 . 160 . 161 . 161 . 162 . 162
iv
IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide
Chapter 8. Policies reference. . . . . 165

About policies . . . . . . . More information about policies . Predefined policies . . . . . R3_Monitor_ABAP_Dumps . . R3_Monitor_Batch_Jobs . . . R3_Monitor_File_Systems . . R3_Monitor_Production_Repairs R3_Start_Buffer_Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 165 165 165 166 166 166 166
Appendix A. IBM Tivoli Enterprise Console event mapping . . . . . . . 167 Appendix B. Commands for utilities
ksanfy . . ksar3nfy . ksar3 . . ksar3exe . ksapwd . ksar3pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
. . . . . . 206 207 210 211 214 215
Examples of trace logging . . . . . . . Principal trace log files . . . . . . . . Setting RAS trace parameters . . . . . . Enabling and disabling RFC tracing . . . . Problems and workarounds . . . . . . . Installation and configuration problem determination . . . . . . . . . . . Agent problem determination . . . . . . Tivoli Enterprise Portal problem determination Workspace problem determination . . . . Situation problem determination . . . . . Take Action command problem determination Support information . . . . . . . . . . Searching knowledge bases . . . . . . . Obtaining fixes . . . . . . . . . . . Receiving weekly support updates . . . . Contacting IBM Software Support . . . . Using IBM Software Services for Tivoli . . .
. . . . .
219 220 222 225 227
. 228 . 232 234 . 235 . 237 240 . 241 . 241 . 242 . 242 . 242 . 244
Appendix D. Accessibility . . . . . . 245

Navigating the interface using the keyboard . Magnifying what is displayed on the screen . . . . 245 . 245
Appendix C. Problem determination

Gathering product information for IBM Software Support . . . . . . . . . . . . . . Built-in problem determination features . . . Problem classification. . . . . . . . . . Trace logging . . . . . . . . . . . . Overview of log file management . . . .
217
. . . . . 217 218 218 218 219
Appendix E. Notices . . . . . . . . 247

Trademarks . . . . . . . . . . . . . . 249
Index . . . . . . . . . . . . . . . 251
Contents
vi
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Requirements for the Monitoring Agent for mySAP . . . . . . . . . . . . . . 5 Viewing real-time data about mySAP . . . . 27 Investigating an event . . . . . . . . . 28 Recovering the operation of a resource . . . 29 Customizing your monitoring environment 29 Monitoring with custom situations . . . . . 31 Collecting and viewing historical data . . . 32 Predefined agent alerts . . . . . . . . . 39 Capacity planning for historical data 135 Overview of event slots to event classes 168 Information to gather before contacting IBM Software Support . . . . . . . . . . 217 Trace log files for troubleshooting agents 220 Trace log problems . . . . . . . . . . 226 Problems and solutions for installation and configuration for agents that run on UNIX and Windows systems . . . . . . . . 228 Problems and solutions for installation and configuration of the Monitoring Agent for mySAP . . . . . . . . . . . . . 230 16. 17. 18. 19. 20. 21. 22. 23. General problems and solutions for uninstallation . . . . . . . . . . . Agent problems and solutions . . . . . . Tivoli Enterprise Portal problems and solutions . . . . . . . . . . . . . Workspace problems and solutions . . . . Specific situation problems and solutions Problems with configuring situations that you solve in the Situation Editor . . . . . . Problems with configuration of situations that you solve in the workspace area . . . . . Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services window . . . . . . Take Action commands problems and solutions . . . . . . . . . . . . . 232 232 235 235 237 238 239
240 240
24.
15.
vii
viii
About this guide

The IBM Tivoli Monitoring for Applications: mySAP Agent Users Guide provides information about configuring and using IBM Tivoli Monitoring for Applications: mySAP Agent. Use the configuration chapter in this guide with the IBM Tivoli Monitoring Installation and Setup Guide to set up the software. Use the information in this guide with the IBM Tivoli Monitoring Users Guide to monitor mySAP resources.
Who should read this guide

This guide is for system administrators who install and use Monitoring Agent for mySAP to monitor and manage mySAP resources. Readers should be familiar with the following topics: v Tivoli Enterprise Portal interface v IBM Tivoli Monitoring application software v IBM Tivoli Enterprise Console (optional) v SAP Basis v Microsoft Windows operating systems v AIX operating systems v Solaris operating systems v HP-UX operating systems v Linux operating systems
What this guide contains

This guide contains the following chapters: v Chapter 1, Overview of the Monitoring Agent for mySAP, on page 1 Provides an introduction to the Monitoring Agent for mySAP. v Chapter 2, Requirements and configuration for the monitoring agent, on page 5 Provides requirements and configuration information specific to the Monitoring Agent for mySAP. v Chapter 3, How to use the Monitoring Agent for mySAP, on page 27 Provides a list of tasks to perform when using the monitoring agent, a list of procedures for performing each task, and references for finding information about the procedures. After completing installation and configuration and becoming familiar with the information in Chapter 1 of this guide, use this chapter to see how you can use the monitoring agent. v Chapter 4, Workspaces reference, on page 33 Provides an overview of workspaces, references to additional information about workspaces, and descriptions of predefined workspaces in this monitoring agent. v Chapter 5, Attributes reference, on page 63
ix
Provides an overview of attributes, references to additional information about attributes, descriptions of the attribute groups and attributes, and disk space requirements for historical data. Chapter 6, Situations reference, on page 141 Provides an overview of situations, references to additional information about situations, and descriptions of the predefined situations in this monitoring agent. Chapter 7, Take Action commands reference, on page 159 Provides detailed information about the Take Action commands, references to additional information about Take Action commands, and descriptions of the Take Action commands provided in this monitoring agent. Chapter 8, Policies reference, on page 165 Provides an overview of policies, references for detailed information about policies, and descriptions of the predefined policies included in this monitoring agent. Appendix A, IBM Tivoli Enterprise Console event mapping, on page 167 Provides an overview of the IBM Tivoli Enterprise Console event mapping information for this monitoring agent. Appendix B, Commands for utilities, on page 205 Provides command reference information for the Monitoring Agent for mySAP utilities. Appendix C, Problem determination, on page 217 Provides information about troubleshooting the various components of the Monitoring Agent for mySAP, information about log files and messages, and information about your options for obtaining software support. Appendix D, Accessibility, on page 245 Provides information about the accessibility features in the Monitoring Agent for mySAP.
v Appendix E, Notices, on page 247 Provides IBM notices and trademark information as it applies to the Monitoring Agent for mySAP.
Publications
This section lists publications relevant to using the Monitoring Agent for mySAP and describes how to access these publications online and how to order these publications.
Prerequisite publications
To use the information in this guide effectively, you must have some knowledge of IBM Tivoli Monitoring products, which you can obtain from the following documentation: v IBM Tivoli Monitoring Installation and Setup Guide v IBM Tivoli Monitoring Problem Determination Guide v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring v Introducing IBM Tivoli Monitoring, Version 6.1.0 v IBM Tivoli Monitoring Administrators Guide v IBM Tivoli Monitoring Users Guide
Related publications
The following documents also provide useful information: v IBM Tivoli Enterprise Console Adapters Guide v IBM Tivoli Enterprise Console Event Integration Facility Users Guide v IBM Tivoli Enterprise Console Reference Manual v IBM Tivoli Enterprise Console Rule Builders Guide
Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: http://www.ibm.com/ibm/terminology
Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: http://www.ibm.com/software/tivoli/library/ Click Tivoli product manuals. In the Tivoli Technical Product Documents Alphabetical Listing window, click IBM Tivoli Monitoring for Applications: mySAP Agent to access your product library at the Tivoli software information center. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper.
Ordering publications
You can order many Tivoli publications online at the following Web site: http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/ pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: 800-879-2755 v In Canada: 800-426-4968 In other countries, contact your software account representative to order Tivoli publications.
About this guide
xi
Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate most features of the graphical user interface. For additional information, see Appendix D, Accessibility, on page 245.
Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: http://www.ibm.com/software/tivoli/education/
Support information
Support information on page 241 describes the following options for obtaining support for IBM products: v Searching knowledge bases on page 241 v Obtaining fixes on page 242 v Contacting IBM Software Support on page 242
Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating system-dependent commands and paths.
Typeface conventions
This guide uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text Italic v v v v Words defined in text Emphasis of words New terms in text (except in a definition list) Variables and values you must provide
Monospace v Examples and code examples v File names, programming keywords, and other views that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user
xii
v Text that the user must type v Values for arguments or command options
Operating system-dependent variables and paths

The direction of the slash for directory paths might vary in this documentation. No matter which type of slash you see in the documentation, use the following guidelines for a slash: v If using UNIX, use a forward slash (/). v If using Windows, use a backslash (\). The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX. For environment variables, use the following guidelines: v If using UNIX, use $variable. v If using Windows, use %variable%. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.
About this guide
xiii
xiv
Chapter 1. Overview of the Monitoring Agent for mySAP

You can use the Monitoring Agent for mySAP to monitor mySAP and to perform basic actions with systems running R/3, R/3 Enterprise, ERP, and mySAP applications. This chapter provides a description of the features, components, and interface options for the Monitoring Agent for mySAP.
IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Monitoring Agent for mySAP. IBM Tivoli Monitoring provides a way to monitor the availability and performance of all the systems in your enterprise from one or several designated workstations. It also provides useful historical data that you can use to track trends and to troubleshoot system problems. You can use IBM Tivoli Monitoring to do the following tasks: v Monitor for exception conditions on the systems that you are managing by using predefined situations or custom situations v v v v Establish your own performance thresholds Investigate the causes leading to an exception condition Gather comprehensive data about system conditions Use policies to perform actions, schedule work, and automate manual tasks
The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. Providing a consolidated view of your environment, the Tivoli Enterprise Portal permits you to monitor and resolve performance issues throughout the enterprise. You can view your enterprise using default physical views or using custom created logical views in the Navigator tree. See the IBM Tivoli Monitoring publications listed in Prerequisite publications on page x for complete information about IBM Tivoli Monitoring and the Tivoli Enterprise Portal.
Features of Monitoring Agent for mySAP

IBM Tivoli Monitoring is the best management tool for the end-to-end mySAP environment, and for the enterprise as a whole. The Monitoring Agent for mySAP enables mySAP performance, availability, monitoring, and historical data to be merged and correlated with your entire enterprise. IBM Tivoli Monitoring provides a centralized console for event correlation, including the following features: v mySAP and non-mySAP data analysis v Take Action commands to correct problems v Application launch to start the SAPGUI and take the administrator to the problem area in the monitored mySAP system v Policies to span mySAP and non-mySAP IBM Tivoli Monitoring agents for problem resolution and task automation v Integration of the Tivoli Enterprise Portal browser into an SAP Enterprise Portal View
v Situation editor for quick monitor attribute changes and to create new situations The IBM Tivoli Monitoring for Applications: mySAP Agent offers a central point of management for gathering the information you need to detect problems early, and to take steps to prevent them from recurring. It enables effective systems management across mySAP releases, applications and components; and the underlying databases, operating systems, and external interfaces. You can easily collect and analyze critical information such as the following about your mySAP enterprise: v Your operating system and the associated local area network (LAN) v Your Oracle databases used by mySAP systems v mySAP memory and buffer performance v Layout and configuration of mySAP application instances, databases, and system components v Batch processing, including batch data create sessions v Performance monitoring reported by mySAP service, transaction, user, application, sub-application, or program v IBM Tivoli Monitoring generated alerts from predefined best practice monitoring situations and SAP CCMS alerts from the systems running mySAP solutions v mySAP user and gateway activity v Transport system activity that might affect the integrity of your development, test, and production systems v Monitor the system using syslog, ABAP system dumps, and developer traces
Components of Monitoring Agent for mySAP

After you install the Monitoring Agent for mySAP as directed in the IBM Tivoli Monitoring Installation and Setup Guide, you have an environment that contains the client, server, and monitoring agent implementation for IBM Tivoli Monitoring that contains the following components: v Tivoli Enterprise Portal client with a Java-based user interface for viewing and monitoring your enterprise. v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli Enterprise Monitoring Server and enables retrieval, manipulation, and analysis of data from the monitoring agents. v Tivoli Enterprise Monitoring Server, which acts as a collection and control point for alerts received from the monitoring agents, and collects their performance and availability data. v Monitoring agent, Monitoring Agent for mySAP, which collects and distributes data to a Tivoli Enterprise Monitoring Server. v Operating system agents and application agents installed on the systems or subsystems you want to monitor. These agents collect and distribute data to the Tivoli Enterprise Monitoring Server. v Tivoli Data Warehouse for storing historical data collected from agents in your environment. The data warehouse is located on a DB2, Oracle, or Microsoft SQL database. To collect information to store in this database, you must install the Warehouse Proxy agent. To perform aggregation and pruning functions on the data, install the Warehouse Summarization and Pruning agent. v Tivoli Enterprise Console event synchronization component for synchronizing the status of situation events that are forwarded to the event server. When the status of an event is updated because of IBM Tivoli Enterprise Console rules or operator actions, the update is sent to the monitoring server, and the updated
status is reflected in both the Situation Event Console and the Tivoli Enterprise Console event viewer. For more information, see IBM Tivoli Monitoring Installation and Setup Guide.
User interface options

Installation of the base software and other integrated applications provides the following interfaces that you can use to work with your resources and data: Tivoli Enterprise Portal browser client interface The browser interface is automatically installed with Tivoli Enterprise Portal. To start Tivoli Enterprise Portal in your Internet browser, enter the URL for a specific Tivoli Enterprise Portal browser client installed on your Web server. Tivoli Enterprise Portal desktop client interface The desktop interface is a Java-based graphical user interface (GUI) on a Windows or Linux workstation. IBM Tivoli Enterprise Console Event management application Manage Tivoli Enterprise Monitoring Services window The window for the Manage Tivoli Monitoring Services utility is used for configuring the agent and starting Tivoli services that are not already designated to start automatically. IBM Tivoli Monitoring command line IBM Tivoli Monitoring commands are run from the command line. They are primarily used in the UNIX environment. They can be used for installing, configuring, starting, and stopping the agent.
Chapter 1. Overview of the Monitoring Agent for mySAP
Chapter 2. Requirements and configuration for the monitoring agent

This chapter contains information about the following major topics and procedures relevant to the installation and configuration of the Monitoring Agent for mySAP: v Requirements for the monitoring agent v Basic installation and configuration of the Monitoring Agent for mySAP on page 6 v Remote deployment on page 14 v Advanced installation and configuration of the Monitoring Agent for mySAP on page 15
Requirements for the monitoring agent

In addition to the requirements described in the IBM Tivoli Monitoring Installation and Setup Guide, the Monitoring Agent for mySAP has the requirements listed in Table 1.
Table 1. Requirements for the Monitoring Agent for mySAP Operating system Operating system versions Windows UNIX
v Windows 2000 Advanced Server v AIX 5.1, 5.2, 5.3 (32-bit and (32-bit) 64-bit) v Windows 2000 Server (32-bit) v Windows 2003 Server EE (32-bit) v Windows 2003 Server SE (32-bit) v Windows 2003 Server EE Datacenter v HP-UX 11i (32-bit and 64-bit) v Solaris 8, 9, 10 (32-bit and 64-bit) v SuSE 8, 9 (32-bit on Intel) v SuSE 8, 9 (64-bit on Linux for zSeries) v RedHat 2.1, 3.0, 4.0 (32-bit on Intel)
SAP Basis and Web Application Server (WAS) levels supported
v 4.6C v 4.6D v 6.10 v 6.20 v 6.30 v 6.40
Table 1. Requirements for the Monitoring Agent for mySAP (continued) Operating system Applications and components supported Windows UNIX
v Advanced Planning and Optimizer (APO), Supply Chain Management (SCM) v Customer Relationship Management (CRM), Enterprise Buyer & Procurement (EBP), Business to Business Procurement (BBP), Supplier Relationship Management (SRM) v R/3, R/3 Enterprise, mySAP Enterprise Resource Planning (ERP) v Exchange Infrastructure (XI) v NetWeaver (NW04) v Business Information Warehouse (BW) v Strategic Enterprise Management (SEM) v Business Intelligence (BI) v Solution Manager (SM)
Memory
v 50 MB RAM per agent instance
v AIX 50 MB per agent instance v HP-UX 50 MB per agent instance v Solaris 50 MB per agent instance v SuSE 50 MB per agent instance v RedHat 50 MB per agent instance
Disk space
v 80 MB disk space for the monitoring agent v Historical data disk space: see Disk capacity planning for historical data on page 134. v 45 MB for RAS1 logging per agent instance
v AIX 80 MB v HP-UX 80 MB v Solaris 80 MB v SuSE 80 MB v RedHat 80 MB v Historical data disk space: see Disk capacity planning for historical data on page 134. v 45 MB for RAS1 logging per agent instance
Other requirements
v For remote administration, IBM Tivoli Monitoring: Windows OS Agent must be installed and running.
For remote administration, the following agents must be installed and running: v IBM Tivoli Monitoring: UNIX OS Agent
v For application launch, the v IBM Tivoli Monitoring: Linux SAPGUI must be installed on OS Agent the Tivoli Enterprise Portal Desktop or on the remote system running the Tivoli Enterprise Portal Browser client.
Basic installation and configuration of the Monitoring Agent for mySAP

Basic installation and configuration of the Monitoring Agent for mySAP consists of procedures for the following purposes: v Installing to the mySAP system on page 7 v Installing to the IBM Tivoli Monitoring system on page 10
v Configuring the Monitoring Agent for mySAP on page 10 v Starting or stopping the Monitoring Agent for mySAP on page 13 Note: You only install and configure one Monitoring Agent for mySAP for each mySAP system, not one agent per application server. Be sure to plan your monitoring, for example determine which situations to use, which CCMS trees to monitor, and so on. Obtain information about requirements from your SAP Administrator. The Monitoring Agent for mySAP is a powerful tool that, when configured correctly, can effectively monitor your mySAP environment. The key is careful planning. Your monitoring team and SAP Administrators must carefully plan the areas to monitor. You must also periodically review and update your plan as circumstances warrant. Follow these guidelines when developing a monitoring plan: v Select the key mySAP applications, transactions, programs, and processes that you want to monitor. v Select specific attributes that represent the most critical aspects of your environment. v Document thresholds and cycle times for each monitoring attribute. v Use historical data collection to trend and predict potential issues. v Prioritize areas you want to monitor. Too much data can cloud analysis and hinder preventive diagnosis. v Review implementation, integration, and business process documentation. v Review past problem areas, outages, and performance degradations. v Consider the entire enterprise and all of the applications, components, services, computers, and infrastructure that enable the critical business operations. v Gather input from as many people as possible. Ensure that the plan addresses the business requirements.
Installing to the mySAP system

On the mySAP system, installation includes installing an SAP transport, defining the user with which the agent is to connect to the mySAP system, and verifying the prerequisites for data collection.
Installing SAP transport and defining the user

The Monitoring Agent for mySAP provides a set of ABAP routines to support data collection in the mySAP system. This ABAP code is delivered as a mySAP transport that must be installed on each mySAP system that is to be monitored. Your SAP Administrator installs the transport. In addition to installing ABAP code, the transport also installs a predefined user ID and authorization profile. These items are installed on the client that was specified when the transport was installed. The authorization profile contains all of the permissions required by the mySAP agent to perform functions in the mySAP system. The user ID is configured to use this authorization profile and it is configured with a default password. This user ID and password are specified as the defaults during agent configuration. If you do not want to use the default user supplied by the Monitoring Agent for mySAP, you can create a user and assign it the predefined authorization profile, ZITM_610AUTH, which provides the minimum authorizations needed to perform data collection.
Some of the code in the transport is specific to the mySAP release. The ABAP code in the transport adjusts to the mySAP level at import time. If you upgrade the mySAP system to a new release (for example, from V4.6 to V6.20) you must reimport the transport in order for the ABAP code to readjust to the new mySAP release level. Note: To protect against unauthorized use, the ABAP code that is installed in the mySAP system is not visible from within the mySAP system. In addition, this code cannot be modified or generated. Support for this code must be obtained through IBM Software Support. In addition to installing ABAP code, the transport also installs translated language text elements to provide NLS support for mySAP transport text elements. This procedure installs the mySAP transport into the mySAP system. 1. Go to the /ABAP directory on the product CD. 2. Copy the transport files into the mySAP environment as follows: a. The transport files are located in the ABAP directory of the Monitoring Agent for mySAP CD or image. There are three sets of transport files: 1) K610_00xxx.ITM and R610_00xxx.ITM These files are non-Unicode versions of the transport. They contain the Monitoring Agent for mySAP ABAP code as well as non-Unicode language support for Latin code pages. Refer to section Non-Unicode double-byte language support on page 24 for additional language support. 2) K610_00xxxU.ITM and R610_00xxxU.ITM These files are Unicode versions of the transport. They contain the Monitoring Agent for mySAP ABAP code as well as Unicode support for text strings for Latin code pages and double-byte code pages. 3) K610_DELETE.ITM and R610_DELETE.ITM These transport files remove the ABAP code. The DELETE transport does not need to be imported, unless you stop using the product entirely and want to remove the transports from their mySAP systems. See Removing remote function modules from mySAP on page 25. b. Determine which transport is required for your mySAP system: Unicode or non-Unicode. c. Copy your transport files to the mySAP Transport System data directory as follows: v Non-Unicode transport 1) Copy the K610_00xxx.ITM file to the cofiles directory. 2) Copy the R610_00xxx.ITM file to the data directory. or v Unicode transport 1) Copy the K610_00xxxU.ITM file to the cofiles directory. 2) Copy the R610_00xxxU.ITM file to the data directory. 3. Run the following commands: v Non-Unicode
tp addtobuffer ITMK610_00xxx SID pf=\usr\sap\trans\bin\PROFILE_NAME tp import ITMK610_00xxx SID client=nnn U16 pf=\usr\sap\trans\bin\PROFILE_NAME
v Unicode
tp addtobuffer ITMK610_00xxxU SID pf=\usr\sap\trans\bin\PROFILE_NAME tp import ITMK610_00xxxU SID client=nnn U16 pf=\usr\sap\trans\bin\PROFILE_NAME
Where: SID Target mySAP system ID
PROFILE_NAME Name of the tp profile file nnn Number for the target client where the agent is to run and in which the user ID, IBMMON_AGENT, and authorization profile, ZITM_610AUTH, are defined.
Note: Make sure the current tp parameter file is specified when importing the agent transport files from the command line. The tp parameter file is typically named tp_domain_SID.pfl. This file name is case sensitive on UNIX. Note: If you are using Central User Administration (CUA), see Central User Administration (CUA) on page 17. Note: Alternately, you can use the mySAP STMS transaction to import the ITMK610_00xxx.ITM and ITMK610_00xxxU.ITM transport requests. Ensure that the Import Transport Request Again and the Overwrite Objects in Unconfirmed Repairs options are checked on the Import Options tab of the Import Transport Request window.
Verifying the prerequisites for data collection

Verify the following prerequisites for data collection: v COLLECTOR_FOR_PERFORMANCE batch job v Oracle data collection v OS Collector on page 10 COLLECTOR_FOR_PERFORMANCE batch job: The Monitoring Agent for mySAP relies on the COLLECTOR_FOR_PERFORMANCE batch job to report Oracle historical statistics. Use transaction SM37 to verify that the COLLECTOR_FOR_PERFORMANCE batch job is set up as described in the mySAP installation documentation and SAP OSS Note 16083. The actual job name might be different on your system. Oracle data collection: Data collection problems might occur when the mySAP program, RSDB_TDB, which collects the Oracle statistics, does not work correctly. Too many data rows are stored in MONI. Collection might stop or run sluggishly on busy systems. See SAP Notes: 591801, 713211. To correct this problem, perform the following steps: 1. Have your SAP Administrator implement these SAP notes. 2. Run the specified program, RSORAUD0, with the recommended cleanup options. 3. Update the Oracle statistics manually through transaction DB02.
After implementing these steps, the number of rows being returned to the agent is correct, the volume of data in MONI does not increase, and agent data collection periods are normal. OS Collector: The Monitoring Agent for mySAP relies on the saposcol program provided by SAP to collect operating system and file system metrics. Have your SAP Administrator enable this service on all computers hosting mySAP application servers.
Installing to the IBM Tivoli Monitoring system

To install the Monitoring Agent for mySAP to the IBM Tivoli Monitoring system, complete the agent installation steps in the IBM Tivoli Monitoring Installation and Setup Guide, Installing monitoring agents.
Configuring the Monitoring Agent for mySAP

To monitor a mySAP system, the Monitoring Agent for mySAP must connect to an application server in the system to be monitored so the agent can access the ABAP code provided with the product. The specification of these connection parameters is the configuration process. This section describes the basic configuration steps for the Monitoring Agent for mySAP on both Windows and UNIX systems. If you want to use remote management (install the Monitoring Agent for mySAP on a computer that is different from the mySAP application server), see the Advanced installation and configuration of the Monitoring Agent for mySAP on page 15. To configure a new instance of the Monitoring Agent for mySAP, perform the following steps: 1. Do one of the following depending on your operating system: v For Windows systems: a. From the Manage Tivoli Enterprise Monitoring Services window, double-click IBM Tivoli Monitoring for Applications: mySAP Agent Template. b. Use the information in Step 2 on page 11 to complete the agent-specific parameters. v For UNIX systems, do one of the following: Use the GUI: a. In the Manage Tivoli Enterprise Monitoring Services window, select Monitoring Agent for mySAP. b. Select Actions > Configure to display the Configured mySAP agents window. c. Select the Create new configuration check box. d. Enter a 3-character identifier. e. Click Configure. f. Use the information in Step 2 on page 11 to complete the agent-specific parameters. or Use the command line: a. Run the itmcmd config command:
itmcmd config -A -o system_identifier sa
10
Where: system_identifier Unique 3-character mySAP system identifier, for example, QA1. This is the same as system identifier on page 11. sa Product code for the Monitoring Agent for mySAP Example:
itmcmd config -A -o QA1 sa
This example command configures the Monitoring Agent for mySAP for a system named "QA1." You can have multiple configurations for the agent, one for each mySAP system ID (SID). Each configuration must be created separately by running the itmcmd config command. b. Complete the parameters for configuring IBM Tivoli Monitoring. c. Use the information in Step 2 to complete the line prompts for the agent-specific parameters. For additional information about the itmcmd config command, see the IBM Tivoli Monitoring Administrators Guide Note: You only need to configure one instance of the agent per mySAP system. You do not need one instance per application server. 2. Use the following values to configure the Monitoring Agent for mySAP: Note: Obtain these values from your SAP Administrator. System identifier Three-character mySAP system identifier (SID). Because there can be more than one instance of the mySAP agent running on this computer, supply a name that can be used to identify this agent instance. The name you supply is displayed in the Task/Subsystem column of the Manage Tivoli Enterprise Monitoring Services window. It is also displayed in the agent name in the Navigator tree of the Tivoli Enterprise Portal. You can use the SID for the mySAP system that you want this agent to monitor. However, there are cases where you might want to supply a different identifier. For example, if you plan to run two instances of the agent on this computer to monitor two different mySAP systems with the same SID, you can supply a different identifier to ensure uniqueness. The identifier is used only as a label. Host name Primary Host name of the mySAP application server to which this agent is to connect. If your mySAP servers communicate over a private LAN, the computers hosting the servers have two or more network cards. For the host name, enter a name by which the application server can be reached from external systems, such as through the SAPGUI logon. Do not use the private LAN host name. The default is the host name on which the agent is installed. Use an application server, such as the central instance, that is highly available in the mySAP system.
11
Alternate 1 (optional) Second choice for host name if the Primary host is unavailable. Alternate 2 (optional) Third choice for host name if both the Primary and Alternate 1 hosts are unavailable. System number Two-digit mySAP system number or instance number, defaults to 00. Gateway name Primary Host name on which the mySAP gateway service runs. Typically, this is the same computer as the application server. Specify the name that you used for the Host name value. Alternate 1 Second choice for Gateway name if Primary host is unavailable Alternate 2 Third choice for Gateway name if both Primary and Alternate 1 gateway hosts are unavailable Gateway service The port number used by the Gateway hosts. The gateway ports are always in the following form: 33xx. The xx value is typically the same as the two-digit System number. Client number mySAP client number for the RFC logon to mySAP, defaults to 000. If the predefined IBM Tivoli Monitoring user generated by ABAP is used, enter the client number that was specified in the transport import. This is the same as the nnn client number on page 9. User ID mySAP user ID for the RFC logon to mySAP, defaults to IBMMON_AGENT, which is the predefined user ID created during the import. Password or Password File Use one of these two options: Password mySAP password for the user ID you specified, defaults to ITMMYSAP. Password File Name of the file from which an encrypted password can be read. (See Using ksapwd and ksar3pwd to encrypt a password on page 19.) If the password file is not in the same directory as the Monitoring Agent for mySAP, specify the full path and file name of the password file. Language Language code that indicates the language that the agent is to use when connecting to the mySAP system. The language specified here determines the language in which you see mySAP information such as alert messages, syslog messages, and job log messages. All mySAP systems are delivered in English and German. If you require a different language, confirm with your SAP Administrator that
12
the language is installed on the mySAP system. Specifying an unsupported language prevents the agent from connecting to the mySAP system. The following languages and codes are supported: v v v v v v v v v v EN - English DE - German FR - French IT - Italian ES - Spanish JA - Japanese KO - Korean PT - Portuguese ZH - Chinese ZF - Traditional Chinese
RFC Trace RFC trace setting for the SAPTRACE variable. Selecting this check box activates RFC tracing, defaults to not checked. For the command line, 0 = No trace and 1 = Do trace. Because RFC tracing generates extensive diagnostic information, it is best used with the guidance of IBM Software Support. View RFC Trace Clicking this option displays the RFC trace. Hide Agent Logon Parms from ITM Setting for the SAPNOLOGONPARMS variable. Selecting this check box sets the SAPNOLOGONPARMS to 1 to prevent the configured Monitoring Agent for mySAP logon parameters (user ID and password) from being sent to the IBM Tivoli Monitoring workstation for security reasons. Clearing the check box for this parameter enables the use of the configured mySAP user ID for tasks other than basic monitoring. Refer to mySAP user IDs on page 16 for a more thorough discussion of mySAP user IDs before changing the default setting. 3. If you are using the GUI, click OK to save the configuration values in the system registry. 4. If you want to create another instance of the Monitoring Agent for mySAP, repeat Steps 1 - 3. Use a unique System Identifier for each Monitoring Agent for mySAP instance that you create.
Starting or stopping the Monitoring Agent for mySAP

You can use the GUI in Windows or UNIX to start and stop the Monitoring Agent for mySAP. For UNIX operating systems, you can also use the command line. When using the command line to start or stop the Monitoring Agent for mySAP, use the -o option to specify which mySAP instance to control. For example:
itmcmd agent -o system_identifier start sa
or
itmcmd agent -o system_identifier stop sa
Where:
13
system_identifier Three-character SAP system ID for the mySAP system For example, the following command starts a mySAP system with the system ID of QA1:
itmcmd agent -o QA1 start sa
For additional information about the itmcmd agent command, see the IBM Tivoli Monitoring Installation and Setup Guide.
Remote deployment
You can deploy the Monitoring Agent for mySAP remotely from the Tivoli Enterprise Portal or from the command line. See the IBM Tivoli Monitoring Installation and Setup Guide for procedural information. See the following sections in this guide for agent-specific parameters: v Deploying the monitoring agent remotely from the Tivoli Enterprise Portal v Deploying the monitoring agent using the tacmd command on page 15
Deploying the monitoring agent remotely from the Tivoli Enterprise Portal
For the mySAP Properties tab, complete the following properties: v mySAP System ID (System identifier) v mySAP Hostname (Host name) v mySAP System Number (System number) v mySAP Client Number (Client number) v mySAP User ID (User ID) v mySAP User Password (Password) v mySAP Language Code (Language) The property names in parentheses correspond to the configuration parameters in Step2 on page 11. For information about these properties, see the descriptions in Step 2 on page 11. Use the following settings for the Agent tab Run as information: Use local system account (Windows only) Select this setting. Allow service to interact with desktop (Windows only) Leave this check box clear. User Name (UNIX only and optional) If the default User ID and password are not to be used (the ones selected when configuring the OS agent), they can be overridden using this field. Group Name (UNIX only and optional) If the default group name is not to be used (the one selected when configuring the OS agent), it can be overridden using this field.
14
Deploying the monitoring agent using the tacmd command

See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd addSystem command. Note: For the addSystem command, all properties are mandatory. Use the -t |--type TYPE parameter to specify the Monitoring Agent for mySAP that you are configuring: SA Use the following parameters for the -p | --properties parameter to configure the Monitoring Agent for mySAP: v INSTANCE (System identifier) v SAPSETTINGS.sap_hostname (Host name)) v SAPSETTINGS.sap_systemno (System number) v SAPSETTINGS.sap_clientno (Client number) v SAPSETTINGS.sap_userid (User ID) v SAPSETTINGS.sap_password (Password) v SAPSETTINGS.sap_language (Language) The parameter names in parentheses correspond to the configuration parameters in Step2 on page 11. For information about these parameters, see the descriptions in Step 2 on page 11. Example:
tacmd addSystem -t SA -n Primary:AMSSAPDEMO1:NT -p INSTANCE=QA1 SAPSETTINGS.sap_hostname=amssapdemo1 SAPSETTINGS.sap_systemno=00 SAPSETTINGS.sap_clientno=100 SAPSETTINGS.sap_userid=IBMMON_AGENT SAPSETTINGS.sap_password=agentpw SAPSETTINGS.sap_language=EN
Advanced installation and configuration of the Monitoring Agent for mySAP

This section covers the following installation and configuration topics: v Remote management on page 16 v mySAP user IDs on page 16 v utilities for the Monitoring Agent for mySAP Using ksar3 and ksar3exe to run automated functions on page 18 Using ksanfy and ksar3nfy to send SAP Office email on page 18 Environment variables in ksar3 and ksanfy script files on page 18 Using ksapwd and ksar3pwd to encrypt a password on page 19 sapshcut command on page 20 v mySAP RFC connections on page 21 v Optional advanced configuration in mySAP on page 21 v Centralized CCMS reporting on page 23 v Non-Unicode double-byte language support on page 24 v Removing remote function modules from mySAP on page 25
15
Remote management
The Monitoring Agent for mySAP performs its functions using SAP Remote Function Calls (RFC). The RFC architecture allows calls between network connected computers. This means that the Monitoring Agent for mySAP does not have to reside on the same physical computer as your mySAP servers. It can reside on a remote computer. You might want to use remote management in the following cases: v When mySAP systems are under strict change control, minimize mySAP system changes by not having the monitoring component on the mySAP computers. v Minimize resource usage (CPU, memory, disk) on the mySAP computers. This can be especially useful if you use intensive historical data collection operations on the Monitoring Agent for mySAP or when mySAP platforms have limited resources for additional operations. v Monitor mySAP systems on any operating system or hardware platform. For example, the Monitoring Agent for mySAP does not run natively on OS/400, but you can manage your OS/400 mySAP systems using remote management. To implement remote management follow these steps: 1. Install the Monitoring Agent for mySAP on a computer or operating system supported by the agent such as Windows 2003 Enterprise Edition. 2. Ensure that there are no firewall limitations between this computer and the mySAP application server to which you want to connect. 3. Configure the agent on this computer. When prompted for the host name and gateway host names, enter the name of the computer on which the mySAP application server is running. 4. Complete the rest of the configuration section. Local management is appropriate in the following environments: v Environments that require other local IBM Tivoli Monitoring operating system and database agents on mySAP systems v Environments with mySAP systems that have sufficient resources for additional operations v Small environments with few mySAP systems
mySAP user IDs

This section provides information about mySAP user IDs and permissions required by the Monitoring Agent for mySAP. User IDs support the following purposes: v Basic agent monitoring v Take Action tasks on page 17 v Launching the SAPGUI on page 17 v Central User Administration (CUA) on page 17
Basic agent monitoring

The Monitoring Agent for mySAP creates a user ID in the mySAP system when the agent transport is imported. This user ID is IBMMON_AGENT. It is preconfigured to be Communications user-only and to use the ZITM_610AUTH authorization profile. This profile, which is created at transport import time, contains the minimal set of permissions to run the agent ABAP code and to take a set of limited actions on your mySAP system.
16
If this user ID name is unacceptable, for example, if it violates your installation naming conventions, you can create a different user ID. The user ID can be any allowable mySAP user ID, but it requires the complete set of permissions in the ZITM_610AUTH profile. The user ID only requires Communication user-only access. The default user ID only provides sufficient authority for the following purposes: v Monitoring and data collection v Closing CCMS alerts v Enabling, disabling, and resetting gateway statistics v Resetting Oracle database statistics If you choose to limit the action capabilities of the agent, you can remove some of the action permissions such as closing CCMS alerts.
Take Action tasks

The agent provides a set of Take Action commands that require additional mySAP permissions. The default user ID does not have permission for these functions. The following Take Action commands are affected: v Cancel Job v Delete Job v Output Request v Start Job If you want to allow the agent to take these actions, you must grant additional permissions to the agent user ID. Alternatively, you can provide a separate user ID with these limited permissions. This user ID can be configured into the mySAP Agent using the ksar3 and ksapwd capabilities. Refer to the following sections for configuration information: v Using ksar3 and ksar3exe to run automated functions on page 18 v Using ksanfy and ksar3nfy to send SAP Office email on page 18 v Using ksapwd and ksar3pwd to encrypt a password on page 19
Launching the SAPGUI

The Monitoring Agent for mySAP provides the ability to open a SAPGUI session directly into the mySAP system from workspace views within the agent. The SAPGUI logon parameters default to the Windows user ID. If you want to allow users to access your mySAP systems and take actions in them, you can provide additional user IDs for this purpose. Any user IDs that you add for launch purposes can be configured into the mySAP agent using the procedures described in sapshcut command on page 20.
Central User Administration (CUA)

If you want to use the predefined user ID and authorization role to monitor a mySAP system set up with Central User Administration, perform one of the following steps: 1. Install the transport into the Central User Administration parent logical system client. 2. Manually create the user ID or role in the client where you want to install the transport. The user ID or role is in the client where the transport is installed (imported).
17
3. Manually create the user ID or role in the Central User Administration parent logical system client and distribute the user ID or role to the client where the agent is to run. 4. Manually create the user ID or role in the Central User Administration parent logical system client and run the agent in this client.
Using ksar3 and ksar3exe to run automated functions

The Monitoring Agent for mySAP provides the ksar3exe utility to enable you to run an action in a mySAP system that you are monitoring. The Monitoring Agent for mySAP provides the ksar3 script (batch or shell) as a wrapper for this utility. The script is used to set or override environment variables required by the utility, in particular the mySAP user ID and password. Always use the script in your automation functions such as Take Action commands, situation actions, and policy actions. Refer to Environment variables in ksar3 and ksanfy script files for further information about setting environment variables in these scripts. Refer to ksar3 on page 210 and ksar3exe on page 211 for detailed command syntax and examples.
Using ksanfy and ksar3nfy to send SAP Office email

The Monitoring Agent for mySAP provides the ksar3nfy utility to enable you to send mail items to SAP Office inboxes in a mySAP system that you are monitoring, in order to deliver information or instructions to administrative users. The Monitoring Agent for mySAP provides the ksanfy script (batch or shell) as a wrapper for this utility. The script is used to set or override environment variables required by the utility, in particular the mySAP user ID and password. Always use the script in your automation functions such as Take Action commands, situation actions, and policy actions. Refer to Environment variables in ksar3 and ksanfy script files for further information about setting environment variables in these scripts. See ksanfy on page 206 and ksar3nfy on page 207 for detailed command syntax and examples.
Environment variables in ksar3 and ksanfy script files

Depending on how you configured the monitoring agent, either all required environment variables, or all required environment variables except SAPUSER and SAPPASSWORD, are passed to the ksar3 and ksanfy scripts from the Tivoli Enterprise Portal. If you did not check Hide Agent Logon Parms from ITM, then SAPUSER and SAPPASSWORD are passed to the scripts. If you checked this option, then SAPUSER and SAPPASSWORD are not passed to the scripts and you must set them in the scripts. Use the information in this section to modify your ksar3 and ksanfy script files to set or override these variables. You can set the following logon environment variables: v SAPHOST (Host name Primary) v SAPGATEWAY (Gateway name Primary) v SAPGATEWAYSERVICE (Gateway service) v SAPLANGUAGE (Language)
18
v v v v v v
SAPTRACE (RFC Trace) SAPSYSTEMNAME (System identifier) SAPSYSTEMNUMBER (System number) SAPCLIENT (Client number) SAPUSER (User ID) SAPPASSWORD (Password)
The variable names in parentheses correspond to the configuration parameters in Step 2 on page 11. For information about these variables, see the descriptions in Step 2 on page 11. SAPPASSWORD can have the following values: Password Plain text password FILE() Instructs the utility to read the encrypted password from the default ksa.pwd file in the current directory. To create this file, refer to Using ksapwd and ksar3pwd to encrypt a password. FILE(file_name) Instructs the utility to read the encrypted password from the file_name file. file_name can be either a simple file name or a path and file name. To create this file, refer to Using ksapwd and ksar3pwd to encrypt a password. ITM() Instructs the utility to obtain the mySAP logon user ID and password from the Tivoli Enterprise Portal. PROMPT(ONCE) Instructs the utility to prompt you for the mySAP logon user ID and password only once. This prompt is reissued only if the Tivoli Enterprise Portal is restarted. PROMPT(EVERY) Instructs the utility to prompt you for the mySAP logon user ID and password each time the utility runs. Note: PROMPT(EVERY) overrides PROMPT(ONCE) which overrides ITM()
Using ksapwd and ksar3pwd to encrypt a password

The Monitoring Agent for mySAP provides the ksar3pwd utility to enable you to encrypt a mySAP password and save it in a file. The Monitoring Agent for mySAP provides the ksapwd script (batch or shell) as a wrapper for this utility. The file created by this utility is used for the following purposes: v As a value to the SAPPASSWORD FILE keyword when using the ksar3 and ksanfy utilities. Refer to Environment variables in ksar3 and ksanfy script files on page 18. v As a value to the Password File variable when configuring the Monitoring Agent for mySAP. Refer to the configuration parameters in Step 2 on page 11. See ksapwd on page 214 and ksar3pwd on page 215 for detailed command syntax and examples.
19
sapshcut command
In most of the Monitoring Agent for mySAP workspace tables, you can right-click on a table row and select Launch. This displays a list of mySAP transactions that are relevant to the IBM Tivoli Monitoring workspace that you are viewing. When you select one of the Launch options, IBM Tivoli Monitoring invokes the mySAP command called sapshcut that in turn brings up the SAPGUI. IBM Tivoli Monitoring passes the appropriate parameters that invoke the selected mySAP transaction on the mySAP system that is being monitored. For this Launch feature to work you must do the following: 1. Install the SAPGUI on the computer where you run the Tivoli Enterprise Portal desktop or browser. This computer must be running a Windows operating system because sapshcut is available on Windows only. Note: The Monitoring Agent for mySAP only supports the Windows SAPGUI, not the JAVA SAPGUI. Add the directory containing sapshcut.exe to your system or user path. sapshcut.exe is installed as part of the mySAP client into the following directory: C:\Program Files\SAP\FrontEnd\SAPgui To add additional directories to the system or user path on Windows, select Control Panel > System > Advanced > Environment Variables. Restart the Tivoli Enterprise Portal desktop or browser after modifying the path. Configure saplogon for any systems to which you want to connect (optional to reduce the number of SAPGUI prompts). Make sure the saplogon description starts with the SID (optional to reduce the number of SAPGUI prompts). By default you are logged onto the SAPGUI as follows: v mySAP system that is being monitored v mySAP client that was specified for the Monitoring Agent for mySAP v Windows user ID
2.
3. 4. 5.
You can override these default logon parameters (client and user) by setting them in a sapshcut.bat file. You can also set the password and other mySAP environment variables in this file. You can create and run a Windows sapshcut.bat file as a front-end to the sapshcut executable. The .bat file must be named sapshcut.bat (or sapshcut.cmd) and must reside in your default path before sapshcut.exe. The following parameters are passed to the sapshcut.bat file when called from a predefined Launch definition: %1 %2 %3 %4 %5 %6 keyword -command transaction_name, for example: SM13 keyword -system mySAP_system_identifier, for example: TV1 keyword -client client_number, for example: 100
20
The following example shows a sample sapshcut.cmd file. In this example, you are using a different user ID and password when sapshcut is run through Application Launch for the mySAP system TV1. All other SAP systems use the default logon parameters.
@echo off set sapshcut="C:\Program Files\SAP\FrontEnd\SAPgui\sapshcut.exe" if "%4" == "TV1" ( %sapshcut% %* -user=myid -password=mypwd ) else ( %sapshcut% %* )
mySAP RFC connections

This section provides background information on the use of RFC connections by the Monitoring Agent for mySAP. Use this information to understand and plan for the RFC connections used by mySAP application servers for internal CCMS polling and CCMS alert data collection. This behavior is specific to SAP RFC architecture. The Monitoring Agent for mySAP opens one dedicated RFC connection to the mySAP system being monitored by the agent. The mySAP system then opens one internal connection per instance for data collection through function modules and programs. If CCMS alerts are being collected by the agent, the mySAP system opens one additional (system internal) RFC connection to each instance for this collection thread. So when data collection starts, one RFC connection for the agent is opened, and up to twice the number of mySAP instances for additional internal system RFC connections are opened. You must ensure that the instance conducting the monitoring can accommodate the additional RFC sessions, especially in large systems with 10 or more instances. When the anticipated RFC load for monitoring might adversely impact system performance and tolerances, adjust the mySAP profile parameter accordingly. Refer to your SAP Administrator and the following SAP Notes: v Terminal Sessions (default setting: 200) 22099 v communication/Gateway/Conversation Settings 887909 316877 384971
Optional advanced configuration in mySAP

Use agent-provided transactions in mySAP to customize a number of agent behaviors. Run the /n/ibmmon/itm_config transaction to access the main configuration menu in mySAP. Select one of the following configuration options: v Maintain ITM generated alerts on page 22 v Maintain default sample periods on page 22 v Maintain log file names on page 22 v Maintain managed groups on page 22 v Select monitor sets and monitors on page 22 Note: Preface all /ibmmon/itm* transactions with /n. Configuration changes made in these transactions are used immediately by the Monitoring Agent for mySAP except for those changes made to maintain managed groups. When the managed group configuration has been changed, the changes are discovered by the Monitoring Agent for mySAP at the next heartbeat.
21
Maintain ITM generated alerts

This transaction is used to enable or disable alerts generated by IBM Tivoli Monitoring and to set warning and critical thresholds. All alerts generated by IBM Tivoli Monitoring are displayed with their current status and threshold values. When you modify alert status and thresholds, the modified values are used at the next sample time.
Maintain default sample periods

This transaction is used to set the default sample period for those attribute groups that support a time span during data collection. The default sample period identifies the length of the data sample period starting from the current time and working back in time. In the Tivoli Enterprise Portal, workspace views that show data from these attribute groups show the Tivoli Enterprise Portal time span symbol in the view. Real time in the time span window indicates that the default sample period set here is to be used for data collection. This transaction is also used to set the sample frequency for the Alerts attribute group. The sample frequency for the Alerts identifies the amount of time between data collection for Alerts. When you modify the sample periods, sample frequency, or both, the modified values are used for the next data collection.
Maintain log file names

This transaction is used to identify which log files to consider for inclusion in IBM Tivoli Monitoring reports that contain log file information. All log files with a name that matches the specified name patterns on the specified instances are included in the report at the next data collection interval.
Maintain managed groups

Use this transaction to maintain IBM Tivoli Monitoring Managed Group definitions. All Managed Group names are passed to the Tivoli Enterprise Portal and displayed in the Managed System Selection Lists. At the time of data collection, only data that matches the Attribute selection conditions are sent to the Monitoring Agent for mySAP to be displayed in reports or used for evaluation in situations and policies. You can use Managed Groups to monitor subsets of information in the mySAP system. This enables you to focus only on the parts of the mySAP system in which you are interested and to ignore other parts that do not concern you. For example, if you are only interested in the response time of transactions that are part of the Financial Application, you can create a Managed Group named Financials, and include only Financial transaction codes in it. Whenever the Financials Managed Group is processed by the Tivoli Enterprise Portal only information that contains the specified transaction codes is considered when displaying a report, evaluating a situation, or evaluating a policy.
Select monitor sets and monitors

This transaction is used to select the CCMS monitors from which IBM Tivoli Monitoring retrieves alerts. By default, the Entire System monitor is selected the first time this window is displayed. You can change the monitor set, the monitor, or both the monitor set and monitor, and then save the configuration. You can select any number of monitors for which to collect CCMS alerts.
22
To turn off CCMS alert collection completely, clear the check boxes for all of the monitors and save this configuration. The agent that is already running reads this configuration and collects the CCMS alerts for the monitors that you selected. However, any CCMS alerts that were already collected by the agent prior to changing the CCMS alerts configuration remain with the agent and IBM Tivoli Monitoring. In addition to selecting monitors and monitors sets, this transaction is used to specify the number of occurrences of an alert type to retrieve, and whether or not to automatically close the older occurrences of the alerts that are not retrieved.
Centralized CCMS reporting

Centralized (CEN) Computing Center Management System (CCMS) is an SAP monitoring capability that allows the CCMS alerts for multiple mySAP systems to be reported to a central monitoring hub. This enables monitoring of the mySAP environment from one CCMS console. Centralized CCMS reporting is best used in the following environments: v Primarily a CCMS operation where CCMS alerts are the only monitoring data needed. v Centralized CCMS, Solution Manager, or both are integral parts of the mySAP environment. v Large mySAP environments with many mySAP systems such as ISV and ISP. v IBM Tivoli Monitoring V5.x integration with Monitoring Agent for mySAP CCMS adapters. The Monitoring Agent for mySAP supports Centralized CCMS for alert reporting only, allowing you to place one Monitoring Agent for mySAP on a Centralized mySAP system and view CCMS alerts for the entire mySAP environment. This support is provided in the following ways: v When reporting CCMS alerts, the agent checks if the alerts are associated with the mySAP system being directly monitored by the agent. If the agent determines that an alert belongs to a different mySAP system, it assumes Centralized CCMS and automatically creates additional R3_Group managed systems. v The <local_SID>-All_CCMS_alerts:Grp managed system is used to report the complete set of alerts from all remote mySAP systems. The value of <local_SID> is the system identifier for the mySAP system being directly monitored. For example, if the local mySAP system is QA1, this group name would be QA1-All_CCMS_alerts:Grp. v The <local_SID>-<remote_SID>_CCMS_alerts:Grp managed system is used to report all alerts for one remote mySAP system. The value of <local_SID> is the system identifier for the mySAP system being directly monitored. The value of <remote_SID> is the system identifier for the remote mySAP system. For example, if the local mySAP system is QA1 and the remote mySAP system is QA2, this group name would be QA1-QA2_CCMS_alerts:Grp. v Each of these managed systems in the Navigator tree has the complete set of workspaces under it, but only the Alerts workspace has meaningful data. The Monitoring Agent for mySAP maintains its definitions of Centralized CCMS groups in the ABAP code in the directly managed mySAP system. You might need to modify these definitions if a mySAP system for which you are receiving centralized alerts is also being monitored directly by another instance of the
23
Monitoring Agent for mySAP, and you do not want to have alerts reported under both systems. You can limit the centralized alert reporting as follows: v Use the /IBMMON/ITM_CONFIG transaction to Maintain Managed Groups. Change the All CCMS alerts group. Remove the remote system from this list by editing the group definition to EXCLUDE the remote system identifier. v Use the /IBMMON/ITM_CONFIG transaction to Maintain Managed Groups. Delete the <remote_SID> CCMS alerts group. For example, if the remote mySAP system is QA2, this group name would be QA2 CCMS alerts. Alternatively, you can use Centralized CCMS to report alerts from all mySAP systems, but prevent alert reporting from each locally install agent. Use the following steps to set up this configuration: v Configure an instance of the Monitoring Agent for mySAP to monitor the Centralized CCMS system. Allow the agent to detect and report all alerts from all remote mySAP systems. v Configure an instance of the Monitoring Agent for mySAP to monitor each remote mySAP system. Disable alert collection and reporting for these agent instances by using the /IBMMON/ITM_CONFIG transaction to Select Monitor Sets and Monitors. Within this function, clear the check boxes for all monitors and save this configuration. The Monitoring Agent for mySAP support for Centralized CCMS can be used in a pure CCMS monitoring environment to view all alerts on a common console, or it can be used with its complete set of functions to provide situations, policies, and Take Action commands for the remote mySAP systems.
Non-Unicode double-byte language support

The Monitoring Agent for mySAP transport includes a number of text elements such as the following: v Text elements obtained from the mySAP system v Text elements displayed on the mySAP system by agent configuration windows When you installed the transports into the mySAP system, you selected either a Unicode transport of a non-Unicode transport. The Unicode transport contains translation support for all languages. The non-Unicode transport contains translation support for the single-byte Latin languages only. Use the procedures in this section to install double-byte language support into a non-Unicode mySAP system. You can install double-byte language support for Japanese, Korean, Simplified Chinese, or Traditional Chinese. You can install only the Monitoring Agent for mySAP language texts for a language that is already installed on your mySAP system and your mySAP system codepage supports the select language. Use the following procedure to install one of these double-byte languages into your non-Unicode mySAP system: 1. Run transaction SA38 by entering program name /IBMMON/ ITM_LOAD_LANGUAGES and pressing F8. (At the initial screen you can click Display Instruction to read the online instructions.) 2. Press F4 to receive a list of available languages. The list contains all languages that are installed on your mySAP system and identifies each language that is provided by the Monitoring Agent for mySAP. 3. Select the language for which you require the Monitoring Agent for mySAP texts.
24
4. Press F8 to install these text elements. Note: Language text elements are normally installed in mySAP systems as final text elements. The process outlined here uses raw translated text to generate text elements in your mySAP system.
Removing remote function modules from mySAP

If you choose to remove the Monitoring Agent for mySAP from your system, use this procedure to remove the remote function modules from your mySAP system: 1. Go to the /ABAP directory on the product CD. 2. Copy the transport files into the mySAP environment as follows: a. The transport files are located in the ABAP directory of the Monitoring Agent for mySAP CD or image. There are three sets of transport files: 1) K610_00xxx.ITM and R610_00xxx.ITM These files are non-Unicode versions of the transport. They contain the Monitoring Agent for mySAP ABAP code as well as non-Unicode language support for Latin code pages. Refer to section Non-Unicode double-byte language support on page 24 for additional language support. 2) K610_00xxxU.ITM and R610_00xxxU.ITM These files are Unicode versions of the transport. They contain the Monitoring Agent for mySAP ABAP code as well as Unicode support for text strings for Latin code pages and double-byte code pages. 3) K610_DELETE.ITM and R610_DELETE.ITM These transport files remove the ABAP code. The DELETE transport does not need to be imported, unless you stop using the product entirely and want to remove the transports from their SAP systems. See Removing remote function modules from mySAP. b. Copy the K610_DELETE and R610_DELETE files to the mySAP Transport System data directory as follows: 1) Copy the K610_DELETE file to the cofiles directory. 2) Copy the R610_DELETE file to the data directory. 3. Run the following commands:
tp addtobuffer ITMK610_DELETE SID pf=\usr\sap\trans\bin\PROFILE_NAME tp import ITMK610_DELETE SID client=nnn U16 pf=\usr\sap\trans\bin\PROFILE_NAME
Where: SID Target mySAP system ID
PROFILE_NAME Name of the tp profile file nnn Number for the target client where the agent is to run
25
26
Chapter 3. How to use the Monitoring Agent for mySAP

After you have installed and configured the Monitoring Agent for mySAP, the agent begins monitoring your resources. This chapter provides information about how you can use the Monitoring Agent for mySAP to perform the following tasks: v View real-time data about mySAP v Investigate an event on page 28 v Recover the operation of a resource on page 28 v Customize your monitoring environment on page 29 v Monitor with custom situations that meet your requirements on page 30 v Collect and view historical data on page 31 For each of these tasks, there is a list of procedures that you perform to complete the task. For the procedures, there is a cross-reference to where you can find information about performing that procedure. Information about the procedures is located in subsequent chapters and appendixes of this users guide and in the IBM Tivoli Monitoring documentation.
View real-time data about mySAP

After the Monitoring Agent for mySAP has been installed, configured, and started, the monitoring agent begins monitoring. Table 2 contains a list of the procedures for viewing the real-time data about mySAP that the monitoring agent collects. The table also contains a cross-reference to where you can find information about each procedure.
Table 2. Viewing real-time data about mySAP Procedure View the hierarchy of your monitored resources from a system point of view (Navigator view organized by operating system type, monitoring agents, and workspaces). View the indicators of real or potential problems with the monitored resources (Navigator view). View changes in the status of the resources that are being monitored (Enterprise Message Log view). IBM Tivoli Monitoring Users Guide: Using workspaces (in Monitoring: real-time and event-based chapter) Chapter 4, Workspaces reference, on page 33 in this guide Where to find information IBM Tivoli Monitoring Users Guide: Navigating through workspaces (in Monitoring: real-time and event-based chapter)
27
Table 2. Viewing real-time data about mySAP (continued) Procedure Where to find information View the number of times an event has been IBM Tivoli Monitoring Users Guide: Using opened for a situation during the past 24 workspaces (in Monitoring: real-time and hours (Open Situation Accounts view). event-based chapter) Chapter 4, Workspaces reference, on page 33 in this guide Chapter 6, Situations reference, on page 141 in this guide Manipulate the views in a workspace. IBM Tivoli Monitoring Users Guide: Using views (in Monitoring: real-time and event-based chapter)
Investigate an event
When the conditions of a situation have been met, an event indicator is displayed in the Navigator. When an event occurs, you want to obtain information about that event so you can correct the conditions and keep your enterprise running smoothly. The situation must be associated with a Navigator Item in order to appear. Table 3 contains a list of the procedures for investigating an event and a cross-reference to where you can find information about each procedure.
Table 3. Investigating an event Procedure Determine which situation raised the event and identify the attributes that have values that are contributing to the alert. Review available advice. Notify other users that you have taken ownership of the problem related to an event and are working on it. Remove the event from the Navigator. Where to find information IBM Tivoli Monitoring Users Guide: Opening the situation event workspace (in Monitoring: real-time and event-based chapter, Responding to alerts section) Chapter 4, Workspaces reference, on page 33 in this guide IBM Tivoli Monitoring Users Guide: Acknowledging a situation event (in Monitoring: real-time and event-based chapter, Responding to alerts section) IBM Tivoli Monitoring Users Guide: Closing the situation event workspace (in Monitoring: real-time and event-based chapter, Responding to alerts section)
Recover the operation of a resource

When you find out that a resource is not operating as desired, you can control it manually or automatically using Take Action commands. Table 4 on page 29 contains a list of the procedures for recovering the operation of a resource and a cross-reference to where you can find information about each procedure.
28
Table 4. Recovering the operation of a resource Procedure Take an action on a resource manually. Where to find information IBM Tivoli Monitoring Users Guide: v Other views (in Custom workspaces chapter, Workspace views section) v Take action: Reflex automation (in Situations for event-based monitoring chapter, Event-based monitoring overview section) Chapter 7, Take Action commands reference, on page 159 in this guide Take an action on a system condition automatically by setting up a situation to run a Take Action command. IBM Tivoli Monitoring Users Guide: Situations for event-based monitoring chapter v Customizing a situation v Creating a situation v Specify an action to take v Distribute the situation Chapter 7, Take Action commands reference, on page 159 in this guide Take multiple actions on system conditions automatically using a policy. IBM Tivoli Monitoring Users Guide: Policies for automation chapter v Creating a policy v Maintaining policies Take actions across systems, monitoring agents, or computers using a policy. v Workflows window Chapter 8, Policies reference, on page 165 in this guide
Customize your monitoring environment

You can change how your monitoring environment looks by creating new workspaces with one or more views in it. Table 5 contains a list of the procedures for customizing your monitoring environment and a cross-reference to where you can find information about each procedure.
Table 5. Customizing your monitoring environment Procedure Display data in tables or charts (views) in Tivoli Enterprise Portal. Where to find information IBM Tivoli Monitoring Users Guide chapters: v Custom workspaces v Table and chart views Display an overview of changes in the status IBM Tivoli Monitoring Users Guide: Message of the situations for your monitored log view (in Situation event views: resources (Message Log View). message log, situation event console, and graphic chapter)
29
Table 5. Customizing your monitoring environment (continued) Procedure Specify which attributes to retrieve for a table or chart so you can retrieve only the data you want by creating custom queries. Where to find information IBM Tivoli Monitoring Users Guide: Creating custom queries (in Table and chart views chapter) Chapter 5, Attributes reference, on page 63 in this guide Build links from one workspace to another. IBM Tivoli Monitoring Users Guide: v Link from a workspace (in Custom workspaces chapter) v Link from a table or chart (in Table and chart views chapter) Identify which predefined situations started running automatically when you started the Tivoli Enterprise Monitoring Server. IBM Tivoli Monitoring Users Guide: What the enterprise workspace shows (in Monitoring: real-time and event-based chapter, Using workspaces section) Chapter 6, Situations reference, on page 141 in this guide Determine whether to run situations as defined, modify the values in situations, or create new situations to detect possible problems. Chapter 6, Situations reference, on page 141 in this guide
Monitor with custom situations that meet your requirements

When your environment requires situations with values that are different from those in existing situations, or when you need to monitor conditions not defined by the existing situations, you can create custom situations to detect problems with resources in two ways: v Create an entirely new situation v Create a situation by copying and editing a predefined situation Note: When you create and run a situation, an IBM Tivoli Enterprise Console event is created. For information on how to define event severities from forwarded IBM Tivoli Monitoring situations and other event information, see the IBM Tivoli Monitoring Administrators Guide. You can specify the following information for a situation: v Name v Attribute group and attributes v Qualification to evaluate multiple rows when a situation has a multiple-row attribute group (display item) v Formula v Take Action commands v Run at startup v Sampling interval v Persistence v Severity v Clearing conditions
30
v Expert Advice v When a true situation closes v Available Managed Systems Table 6 contains a list of the procedures for monitoring your resources with custom situations that meet your requirements and a cross-reference to where you can find information about each procedure.
Table 6. Monitoring with custom situations Procedure Create an entirely new situation. Where to find information IBM Tivoli Monitoring Users Guide: Creating a new situation (in Situations for event-based monitoring chapter, Creating a situation section) Chapter 5, Attributes reference, on page 63 in this guide Create a situation by copying and editing a predefined situation. IBM Tivoli Monitoring Users Guide: Customizing a situation (in Situations for event-based monitoring chapter) Chapter 6, Situations reference, on page 141 in this guide Chapter 5, Attributes reference, on page 63 in this guide Run a situation on a managed system. IBM Tivoli Monitoring Users Guide: Situations for event-based monitoring chapter v Associating situations with Navigator items v Distribute the situation (in Customizing a situation section) v Starting, stopping, or deleting a situation
Collect and view historical data

When you collect historical data, you specify the following configuration requirements: v Attribute groups for which to collect data v Collection interval v Summarization and pruning of attribute groups v Roll-off interval to a data warehouse, if any v Where to store the collected data (at the agent or the Tivoli Enterprise Monitoring Server) Table 7 on page 32 contains a list of the procedures for collecting and viewing historical data and a cross-reference to where you can find information about each procedure.
31
Table 7. Collecting and viewing historical data Procedure Configure and start collecting short-term data (24 hours). Configure and start collecting longer-term data (more than 24 hours). View historical data in the Tivoli Enterprise Portal. Create reports from historical data using third-party reporting tools. Filter out unwanted data to see specific areas of interest. Where to find information IBM Tivoli Monitoring Users Guide: Historical reporting (in Table and chart views chapter) IBM Tivoli Monitoring Administrators Guide Disk capacity planning for historical data on page 134
32
Chapter 4. Workspaces reference

This chapter contains an overview of workspaces, references for detailed information about workspaces, and descriptions of the predefined workspaces included in this monitoring agent.
About workspaces
A workspace is the working area of the Tivoli Enterprise Portal application window. At the left of the workspace is a Navigator that you use to select the workspace you want to see. As part of the application window, the right side of the status bar shows the Tivoli Enterprise Portal server name and port number to which the displayed information applies, and the ID of the current user. When you select an item in the Navigator tree, a default workspace is displayed. When you right-click a Navigator item, a menu that includes a Workspace item is displayed. The Workspaces item contains a list of workspaces for that Navigator item. Each workspace has at least one view. Some views have links to other workspaces. Every workspace has a set of properties associated with it. This monitoring agent provides predefined workspaces. You cannot modify or delete the predefined workspaces, but you can create new workspaces by editing them and saving the changes with a different name.
Monitoring Agent for mySAP Navigator tree

The IBM Tivoli Monitoring for Applications: mySAP Agent provides a variety of default workspaces. These workspaces are displayed in the Navigator tree under the following mySAP Agent subnodes: :Ins subnode Contains instance level workspaces :Sys subnode Contains system level workspaces :Grp subnode Contains both instance and system level workspaces A table view within a workspace corresponds to a group of attributes; the columns in the table view shows some or all of the attributes available for the creation of situations.
Predefined launch definitions

Some workspace table views contain predefined launch definitions that enable you to a specific transaction on the mySAP system being monitored. These launch definitions bring up the SAPGUI on the Tivoli Enterprise Portal client. The predefined transactions are those that might be helpful in analyzing the mySAP data shown on a particular workspace. See the IBM Tivoli Monitoring Users Guide for information about how to work with launch definitions. See sapshcut command on page 20 for information about how to configure sapshcut to work with the launch feature.
33
Action links
Some workspace table views have action links. These links perform some action on the mySAP system related to the data being displayed. The link takes you to a new Results workspace that displays the status and result of executing the requested action. The following action links are included: v Close Alert v Close Alerts of the same type v Refresh Database Statistics v Enable Gateway Statistics v Reset Gateway Statistics v Disable Gateway Statistics Note: These action links differ from regular workspace links because they result in an action taking place.
Time spans
The Monitoring Agent for mySAP workspace views are designed to present both summary and detailed information. You might find in some workspaces that the summary and detailed workspaces appear to present different data. This can happen when the views are reporting data over different time spans. The following guidelines apply to Monitoring Agent for mySAP views and time spans: v By default, all views report real time data. In this case, all views in a workspace report a consistent set of information. v Views that support extended time span reporting show the Tivoli Enterprise Portal time span symbol in the view. v When you use the time span option to collect more data for a view, it only affects that view. Summary views continue to report real time data only. In this case, the views might appear to show different information. v The real time interval varies for each attribute group. You can change the real time interval using the configuration transaction in mySAP provided by the Monitoring Agent for mySAP. See Maintain default sample periods on page 22. You can also change the real time interval for the attribute group from the Tivoli Enterprise Portal by using the predefined Launch definition, Sample Periods for ITM Reports. See Predefined launch definitions on page 33 for setup information.
More information about workspaces

For more information about creating, customizing, and working with workspaces, see the IBM Tivoli Monitoring Users Guide. For a list of the predefined workspaces for this monitoring agent and a description of each workspace, refer to the Predefined workspaces section below and the information in that section for each individual workspace.
34
Predefined workspaces
The Monitoring Agent for mySAP provides the following predefined workspaces, which are organized by Navigator item: v :Ins Instance Configuration - Instance Configuration (default) Alerts - Alerts (default) - Close Alert Results (linked) - Close All Alerts Results (linked) Work Processes - Work Processes (default) Operating System - Operating System and LAN (default) - Historical Operating System File Systems - File Systems (default) Buffers and Memory - Buffer Performance (default) - Memory - Number Range Buffer Workload Performance - Service Response Time (default) - Transaction Performance - User Transaction Performance - User Performance - Application Performance - Sub-Application Performance - Historical Service Response Time User Activity - Active Users (default) - Logon Information - User Information (linked) Gateway Statistics - Gateway Statistics (default) - Disable Gateway Statistics Results (linked) - Enable Gateway Statistics Results (linked) - Reset Gateway Statistics Results (linked) Log and Traces - System Log (default) - Developer Traces - System Log Detail (linked) v :Sys System Summary
35
- System Summary (default) Locks and Updates - Enqueue Locks (default) - Asynchronous Updates Batch Processing - Batch Jobs (default) - Batch Data Create - Batch Data Create Log (linked) - Batch Job Log (linked) Spool and Output - Spool Requests (default) - Spool Output (linked) - Output Requests Document Interchange - Transactional RFC (default) - Data Transfer Information Document Archiving - Archive Monitor (default) Logon and Server Groups - Logon Groups (default) SAP Office - SAP Office Inbox (default) Database - Database (default) - Refresh Database Statistics Results - Historical Database Transport Requests - Transport Requests (default) - Transport Objects and Steps (linked) - Transport Log (linked) Logs and ABAP Dumps - ABAP Dumps - Database Logs - SAProuter Log
The remaining sections of this chapter contain descriptions for each of these predefined workspaces. The workspaces are organized alphabetically. The descriptions of each workspace apply to the default settings (the components of the workspace in its original configuration). Any changes or updates that you make to a workspace might not be reflected in the description of the workspace.
ABAP Dumps workspace

ABAP Dumps is the default workspace for the Logs and ABAP Dumps navigator group. The ABAP Dumps workspace provides status information for each mySAP
36
ABAP dump generated for the mySAP managed system that you are monitoring. ABAP Dumps is a predefined workspace that contains the following specific information for each dump: v Program associated with the dump v Host computer where the dump originated v User who created the dump v Date and time the dump was created v Names of the instances associated with ABAP dumps v Summary count of dumps by program v Summary count of dumps by user You can use the data for specific dumps for the following purposes: v Identify the number of ABAP dumps generated for a specific mySAP instance v Identify runtime problems that are occurring on your system The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v ABAP Dump Analysis (ST22) v Sample Period for ITM Reports
Active Users workspace

Active Users is the default workspace for the User Activity navigator group. This predefined workspace provides the following information about all users currently logged on to your mySAP instance: v Summary count of users by client v Summary count of all sessions by user v Complete list of logged on users v Terminal name and address for each user v Session start time for each user v Current transaction for each user v Memory usage for each user v Transactions currently being run by each user You can use the session data for specific users for the following purposes: v Learn about who is logged onto your system v Determine if the user load is correctly spread across all the servers v Anticipate and plan for optimal performance on your mySAP system components The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: User List (SM04) All user entries listed in the workspace have predefined Link options. You can use the link options to perform the following action: v Get detailed user information This option links to the User Information workspace, allowing you to see more detailed information about the logged on user.
37
Alerts workspace
Alerts is the default workspace for the Alerts navigator group. Alerts is a predefined workspace that provides a comprehensive view of SAP Computing Center Management System (CCMS) alerts occurring on the mySAP systems you are monitoring. This workspace displays all alerts reported by CCMS and all alerts reported by the Monitoring Agent for mySAP. The following specific information is provided for each alert: v Date and time the alert occurred v Severity level of the alert, either critical or warning v Message text associated with the alert v Identifying information, such as the alert number and class, assigned by mySAP v Identifier to show whether the alert was raised by the Monitoring Agent for mySAP or by SAP CCMS v Summary count of alerts by severity v Summary count of alerts by class You can use the alert data for mySAP systems collected by the Monitoring Agent for mySAP for the following purposes: v Review the severity of an alert and plan corrective action v v v v Identify system conditions that result in poor performance Learn more about an alert by reviewing its message and class Predict potential problem areas Initiate Tivoli Enterprise Portal policies and situations that initiate Take Action commands to correct problems
All alerts listed in the workspace have predefined Link options. You can use the link options to perform the following actions: v Close Alert. This action closes the selected alert in the mySAP system and displays the results in the Close Alert Results workspace. v Close Alerts of the same type. This action closes the selected alert in the mySAP system. In addition, it closes all other alerts in the mySAP system that are members of the same CCMS MTE class. The results of this action are displayed in the Close All Alerts Results workspace. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v CCMS Monitoring (RZ20) v Performance, SAP Statistics, Workload (ST03) v DB Performance Monitor (ST04) v Operating System Monitor (ST06) v Statistics Display for All Systems (STAD) v Thresholds for ITM Generated Alerts v Sample Periods for ITM Reports For each alert with a severity of warning, a system administrator can evaluate the conditions that caused the alert and consider available options for taking corrective action.
38
For each alert with a severity of critical, a system administrator can evaluate the conditions that caused the alert and plan immediate corrective action. The following actions are possible: v Identifying and reconfiguring instances with heavy usage v Rebalancing system loads v Supplying application instances with additional memory v Correcting archiving problems v Executing Take Action commands that perform corrective maintenance operations on the SAP systems The difference between Close Alert and Close Alerts of the same type applies only when acting on CCMS alerts. When acting on an agent predefined alert, Close Alert and Close Alerts of the same type behave the same.
Special alerts generated by the Monitoring Agent for mySAP

In addition to reporting alerts from CCMS, this workspace also reports internal alerts raised by the agent itself. These predefined agent alerts are listed in Table 8.
Table 8. Predefined agent alerts Alert number 9900 Alert severity Critical Alert class System Alert message Lost connection to mySAP system SSS SSS = SID 9901 9902 9903 Critical Critical Warning (nn > 0) Critical (nn => 10) Warning (nn => 5) Critical (nn => 10) Update Update Update Updates not active Terminated updates nn updates pending nn = number Printer nn output requests pending for printer PPPP nn = number PPPP = printer 9905 9906 9907 Critical Critical Warning (nn => 1) Critical (nn => 2) System System Database Logon not possible Spool consistency check failed nn Oracle exclusive lock waits nn = number 9908 Warning (nn => 30) Critical (nn => 60) Database Oracle exclusive lock wait pending nn seconds nn = number 9909 Critical System Statistics file too large (The mySAP statistics file is over twice the size that it should be.)
9904
39
Table 8. Predefined agent alerts (continued) Alert number 9910 9911 Alert severity Warning Warning (nnnn > 1000) Critical (nnnn => 1500) Alert class System Tivoli Alert message Performance collector job not running Excessive data collected for workspace, nnnn rows deleted workspace = workspace name nnnn = number 9912 Critical CCMS Alerts CCMS alerts collection did not complete. Last started at HH:MM:SS on MM/DD/YYYY Operating system collector (saposcol) error occurred eeeeee Oracle statistics are not available, verify performance collector job is running
9913
Critical
System
9914
Critical
Database
Alert timestamps
When viewing CCMS alerts in the Tivoli Enterprise Portal, it is important to understand the meaning of the Occurrence Time attribute, what influences its value, and how it affects the information you see. This is particularly important when monitoring mySAP systems across large geographic areas. v All CCMS alerts have two timestamps associated with them: user time and Greenwich Mean Time (GMT). Both of these timestamps are available in the Monitoring for mySAP Agent. User time is reported as Occurrence Time; GMT is reported as Occurrence Time GMT. v When viewing CCMS alerts in the Tivoli Enterprise Portal, the default workspace displays alerts using only Occurrence Time. v The value of Occurrence Time is based on the mySAP user ID used to retrieve the alerts. You specify this user ID when you configure the Monitoring for mySAP Agent for a mySAP system. The default user ID is IBMMON_AGENT. v The value of Occurrence Time is also based on the Time Zone setting in the mySAP system for this mySAP user ID. By default, the IBMMON_AGENT Time Zone setting is the mySAP system Time Zone, which is generally the time zone in which the SAP servers reside. This might not be the time zone in which you are viewing the Tivoli Enterprise Portal, so you might not be certain about how old the alerts are. v If you are viewing alerts and the Occurrence Time does not meet your expected times, you can do any of the following: To see the alerts in your local time, have the SAP Administrator change the time zone of the user ID to match your local time zone. This can be done by changing the default user ID (IBMMON_AGENT) or by creating a new user ID specifically for your use with the mySAP Agent. When you see the alerts,
40
the times are relative to your local time, so you can determine exactly how old they are. This approach is recommended if all the servers in one mySAP system reside in the same time zone. You can view all alerts in GMT. To do this, modify the Alert workspace to report the Occurrence Time GMT attribute. This requires that you mentally adjust the alerts times based on the time difference between your time zone and GMT. This approach might be required if the servers in one mySAP system are distributed across multiple time zones.
Application Performance workspace

Application Performance is a predefined workspace that contains the following specific information about application performance for each instance: v Application v Description v Number of dialog steps v Average and total response time, CPU time, wait time, and database request in milliseconds v Total database bytes requested in KB v Total number of database calls Use this workspace to gauge how important business applications are performing. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03) v Sample Periods for ITM Reports
Archive Monitor workspace

Archive Monitor is the default workspace for the Document Archiving navigator group. Archive Monitor is a predefined workspace that provides the following information about data in the Archive Monitor: v Number of open asynchronous errors v Archive device status information v Number of open spool requests v Number of background archiving jobs that are active v Number of background jobs scheduled v Number of archiving errors You can use the data for specific instances for the following purposes: v Learn about the number of errors on the system v Reduce the potential for bottlenecks and future trouble spots v Anticipate and plan for optimal performance on your mySAP system components The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: ArchiveLink: Monitoring (OAM1)
41
Asynchronous Updates workspace

Asynchronous Updates is a predefined workspace that provides information on the status of pending and failed database update requests. You can use this information to identify failed database updates that need to be re-processed or deleted. This workspace includes the following information: v Server on which database updates are occurring v User ID of the person performing the update requests v Status of the update request v v v v v Type of error that occurred during an update Name of the function module for the program executing the update request Program executing the update request Summary count of updates by status Summary count of failed updates by program
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Update Records (SM13) v Sample Periods for ITM Reports You can use the data for the following purposes: v Database capacity planning and database troubleshooting v Building Take Action commands to restart failed updates
Batch Data Create Log workspace

Batch Data Create Log is a predefined workspace that contains the following specific information about a batch data create session: v Session name v Execution host v Transaction v Screen number v Message number and text After reviewing the information in this workspace, return to the Batch Data Create workspace to continue reviewing other batch data create requests. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Batch Input Monitoring (SM35) v Sample Periods for ITM Reports
Batch Data Create workspace

Batch Data Create (BDC) is a predefined workspace that provides information about the contents of BDC sessions and metrics that enable you to monitor the status of a session. You can use the Batch Data Create workspace to review the contents of defined BDC sessions and monitor their progress. The following information is included for BDC sessions: v Summary count of sessions by status v Name of session including its status, such as being created, in error, or completed
42
v v v v
Date and time the session was created, and by whom Date and time the session was most recently modified Start mode for the session, such as automatic or manual Metrics for transactions and screens associated with this BDC session
You can use the data in the Batch Data Create workspace for the following purposes: v Anticipate scheduling conflicts for BDC sessions running in your mySAP system v Reduce the risk for system bottlenecks and trouble spots v Identify sessions with errors for manual correction All batch data create sessions listed in the workspace have predefined Link options. You can use the link options to perform the following action: v View batch data create log This option links to the Batch Data Create Log workspace in which you can view detailed information about the batch data create processing. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Batch Input Monitoring (SM35) v Sample Periods for ITM Reports
Batch Job Log workspace

Batch Job Log is a predefined workspace that shows the log for a given batch job. This workspace contains the following specific information about a batch job: v Job name v Job number v Message number v Message time v Message text After reviewing the information in this workspace, return to the Batch Jobs workspace to continue reviewing other batch jobs. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Job Selection (SM37) v Sample Periods for ITM Reports
Batch Jobs workspace

Batch Jobs is the default workspace for the Batch Processing navigator group. The Batch Jobs workspace provides information about defined batch jobs that are scheduled to run or completed running on your mySAP systems. You can use the Batch Jobs workspace to evaluate information about completed and scheduled batch processing and plan for adjustments to improve performance. This predefined workspace provides the following information about defined batch jobs on your mySAP systems: v Summary count of all jobs by job class v Summary count of all jobs by job completion status v Job name and class
43
v Status of the job, such as defined, scheduled, or active v Identifying information for the system executing the job v Start and end time for the job, including the most recent changes in its scheduling v Name of the person who defined the job initially v Name of the person who has made recent changes in its scheduling All batch jobs listed in the workspace have predefined Link options. You can use the link options to perform the following action: v View batch log This option links to the Batch Job Log workspace in which you can view detailed information about the batch job processing. You can use this workspace for the following purposes: v View and troubleshoot batch job problems v Anticipate scheduling conflicts v Build take actions to rerun critical jobs The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Job Selection (SM37) v Sample Periods for ITM Reports
Buffer Performance workspace

Buffer Performance is the default workspace for the Buffers and Memory navigator group. The Buffer Performance workspace provides information about the performance of buffers on your mySAP systems. You can use the Buffer Performance workspace to evaluate information about anticipated buffer performance and to plan for adjustments to improve performance. Buffer Performance is a predefined workspace that provides the following information about the performance of buffers on your mySAP systems: v Hit ratio for the buffer you are monitoring v Number of buffer requests, hits, and misses v Number of times requested information was not available in the buffer v Buffer space allocated and the space available, in KB v Number of directory entries allocated and those available v Number of objects and number of frames swapped v Number of buffer resets, as well as the date and time that the last reset occurred v Number of objects in the buffer v Number of inserts, changes, and deletes for each monitored object You can use the buffer performance data for your mySAP systems for the following purposes: v Monitor buffer performance and anticipate necessary adjustments to improve future performance v Reduce the size of over allocated and underutilized buffers v Build Take Action commands from situations and policies to tune and adjust buffer resources
44
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Setups/Tune Buffers (ST02)
Close Alert Results workspace

Close Alert Results is a predefined workspace that displays the results of closing a single mySAP alert. After seeing these results, you can return to the Alerts workspace to see the updated list and to continue handling other open alerts.
Close All Alerts Results workspace

Close All Alerts Results is a predefined workspace that displays the results of closing all alerts in a CCMS MTE class. Confirm that all alerts closed successfully. After seeing these results, you can return to the Alerts workspace to see the updated list and to continue handling other open alerts.
Database workspace
Database is the default workspace for the Database navigator group. This predefined workspace reports database metrics for Oracle databases. It displays the database instance and the type of objects in it. If your mySAP system is not using an Oracle database, then this workspace does not display any information about your database. This workspace provides summary and detailed information about your database. Summary information reports the following information that is aggregated by major object type: v Number of objects of this type v Size information Detailed information reports the following information for each object in the database: v Object name and type v Status v Size information You can use the database metrics for your mySAP systems for the following purposes: v Build Take Action commands from situations and policies to automatically resolve potential database problems v Identify objects that will fail on the next attempt to extend them v Identify objects that are in too many extents v Anticipate bottlenecks and trouble spots in database performance v Plan changes to improve database performance v Create situations that generate alerts that notify you of potential trouble spots in database performance
45
This workspace supports a predefined Link option. You can use the link option to perform the following action: v Refresh database statistics This option opens the Refresh Database Statistics workspace, and submits job RSORAT0D to the mySAP system for processing. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Tables and Indexes Monitor (DB02) v DB Performance Monitor (ST04)
Data Transfer Information workspace

Data Transfer Information is a predefined workspace that contains data transfer information pertaining to Intermediate Documents (IDocs) and Electronic Data Interchange (EDI) files. This workspace contains the following information about IDocs: v Summary count of IDocs by their current status v Summary count of IDocs by transfer partner v Date and time the IDoc was created v IDoc status description v Logical message type v IDoc partner port This workspace contains the following information about EDI files: v Number of the record within a file that was last processed successfully v Path and file name of the EDI file being processed v Name of the mySAP system being monitored Review the information in the Data Transfer Information workspace to monitor the flow of Intermediate Documents into and out of your mySAP system. You can identify errors that can affect the timely update of production data in the local or the remote mySAP system, or in external applications. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Display IDoc (WE02) v IDoc Lists (WE05) v IDoc Statistics (WE07) v Status File Interface (WE08) v Sample Periods for ITM Reports
Database Logs workspace

Database Logs is a predefined workspace that contains data from the Database Backup Log file, the Database Archive Log file, and the SAPBA log file. This workspace helps you monitor specific information that can indicate if errors occurred, for example, in backing up the database. For the selected managed system, this workspace includes information such as the following: v Text from each Database Log file v Name of the log file
46
v Date and time the data was collected You can use this data for the following purposes: v Build Take Action commands from situations and policies to alert database staff about database errors, initiate corrective action, or start preliminary actions to mitigate potential database problems v Determine if your database is reporting errors. If so, contact your database administrator with this information. v Examine the log data for new or unexpected messages and investigate why they are occurring. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v DBA Operation Logs (DB14) v Sample Periods for ITM Reports v Log File Names for ITM Reports
Developer Traces workspace

Developer Traces is a predefined workspace that contains data from the developer trace files and the error files so that you can monitor specific messages that can indicate a problem. This workspace includes the following information: v Data lines from the trace or the error file v Name of the mySAP instance being monitored v Name of the trace file or of the error file You can use the Developer Traces workspace to review error messages pertaining to mySAP system. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Display Developer Traces (ST11) v Sample Periods for ITM Reports v Log File Names for ITM Reports
Disable Gateway Statistics Results workspace

Disable Gateway Statistics Results is a predefined workspace that provides status information on a request to disable gateway statistics. A message that indicates that the statistics were disabled is displayed. Ensure that gateway statistics were disabled. After seeing these results, you can return to the Gateway Statistics workspace, but you cannot see any gateway statistics information because this collection is now disabled.
Enable Gateway Statistics Results workspace

Enable Gateway Statistics Results is a predefined workspace that provides status information on a request to enable gateway statistics. A message indicating that the statistics were enabled is displayed. Ensure that gateway statistics were enabled.
47
After seeing these results, you can return to the Gateway Statistics workspace to see the available gateway statistics information.
Enqueue Locks workspace

Enqueue Locks is the default workspace for the Locks and Updates navigator group. Enqueue Locks is a predefined workspace that provides lock statistics that you can use to review lock information for work processes on specific instances. This workspace includes the following information: v Number of locks held v User ID of the person locking a process v Name of the object being locked Viewing lock statistics in this workspace helps you to protect concurrent access to work processes. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Display and Delete Locks (SM12)
File Systems workspace

File Systems is the default workspace for the File Systems navigator group. File Systems is a predefined workspace that provides the following information about the configuration and usage of the file systems on the mySAP instance you are monitoring: v Name of the file system v Allocated capacity of the file system, including space used and space available v Text describing the file system status, for example, static or dynamic v Estimated number of days for file systems to become full You can use the file system data for your mySAP systems for the following purposes: v Anticipate trouble spots in management of your file systems v Plan for changes to your file system allocation to improve performance v Create situations that generate alerts to notify you of potential trouble spots in your file systems, such as the system is filling rapidly The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v CCMS Monitoring (RZ20) v Local Operating System Activity (OS06)
Gateway Statistics workspace

Gateway Statistics is the default workspace for the Gateway Statistics navigator group. Gateway Statistics is a predefined workspace that provides the following statistical information for the specific mySAP instance that you are monitoring: v Connection identifier v Remote host name v Number of connections on the mySAP Gateway v Local TCP/IP address v Local APPC version
48
v v v v v
Local transaction program name Connection number Remote logical unit name User ID of the person connected to the Gateway Number of errors encountered by the Gateway
All gateway connections listed in the workspace have predefined Link options. You can use the link options to perform the following actions: v Enable statistics. This option causes the mySAP system to start collecting statistics for this gateway connection. Use this option if the workspace reports no data available for a gateway connection. Gateway statistics are intended to be enabled for a short period of time during specific analysis. Enabling gateway statistics for a long period of time can result in the gateway statistics values becoming too large to report. v Disable statistics. This option causes the mySAP system to stop collecting statistics for this gateway connection. v Reset gateway statistics. This option causes the mySAP system to reset its gateway statistics counters to zero. Use this option to get the most recent information about the gateway connection. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Gateway Monitor (SMGW)
Historical Database workspace

Historical Database is a predefined workspace that provides the same information as the summary information in the Database workspace, but at historically spaced time intervals.
Historical Operating System workspace

Historical Operating System is a predefined workspace that provides the same information as the Operating System and LAN workspace, but at historically spaced time intervals.
Historical Service Response Time workspace

Historical Service Response Time is a predefined workspace that provides the same information as the Service Response Time workspace, but focused on Dialog response time, at historically spaced time intervals.
Instance Configuration
Instance Configuration is the default workspace for the Instance Configuration navigator group. Instance Configuration is a predefined workspace that provides an overview of the configuration of a mySAP instance. The following information is included: v Number and type of mySAP configured services v Name and TCP/IP address for application instances You can use the configuration data for application instances for the following purposes: v Build Take Action commands to initiate external tools for capacity management and provisioning
49
v Evaluate the current configuration of your mySAP system components v Review the current configuration of mySAP services, such as batch, dialog, enqueue, gateway, message, spool, and update v Reduce the potential for bottlenecks and future trouble spots v Anticipate and plan for optimal performance on your mySAP system components The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Work Process Overview (SM50)
Instance Summary workspace

Instance Summary is the default workspace for the agent subnode Navigator item. This predefined workspace provides the following summary information about a mySAP instance: v Number of work processes by type v Number of critical and warning mySAP CCMS alerts v CPU utilization on the instance server v Number of logged on users by client v Average response on this instance by program Use this information in this workspace to guide you in examining more detailed aspects of this instance.
Logon Groups workspace

Logon Groups is the default workspace for the Logon and Server Groups navigator group. Logon Groups is a predefined workspace that provides Logon Group and Server Group statistics that you can use to monitor individual groups. This workspace includes the following information: v Maximum allowed response time for a particular instance in this Logon group v Number of events occurring per minute on an instance v Maximum number of users allowed in this Logon group for a particular instance You can use the data for specific logon groups to identify system load problems. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Maintain CCMS Logon Groups (SMLG) v Maintain RFC Server Group Assignment (RZ12)
Logon Information workspace

Logon Information is a predefined workspace that provides user logon and user logoff statistics so that you can monitor the security of your system. Specifically, this workspace includes the following information: v List of users who are currently locked v List of users who currently have failed password attempts v Chronological log of all logon and logoff activity to this instance over a specified time span, showing user ID, the action taken, and additional detailed information
50
Use this workspace to maintain security throughout your mySAP system. If this information indicates an unusually high number of unsuccessful logon attempts for a particular user, immediately evaluate why this is occurring, then take prompt action to resolve this possible breach of security. Use this workspace to quickly determine if a user is having trouble logging on because the user ID is locked. If the user ID is locked, determine why. If the user ID must be unlocked, enter the mySAP system to unlock the ID. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Sample Periods for ITM Reports
Memory workspace
Memory is a predefined workspace that contains the following specific information about non-buffer memory areas: v Size allocated, used, and free in KB and percentage v Maximum used in KB and percentage The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: v Setups/Tune Buffers (ST02) v Local Operating System Activity (OS06)
Number Range Buffer workspace

Number Range Buffer is a predefined workspace that contains the following specific information about the number range buffer for the instance: v Maximum and current number of entries v Maximum and current number of indexes v Buffer size v Number of Buffer, Get, Server, and Database calls v Number of conflicts v Number of timeouts v Number of Buffer responses less than 50 microseconds, less than 1 millisecond, and greater than 1 millisecond v Number of server responses less than 1 millisecond, less than 50 milliseconds, and greater than 50 milliseconds v Sample time The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Number Range Buffer (SM56)
Operating System and LAN workspace

Operating System and LAN is the default workspace for the Operating System navigator group. Operating System and LAN is a predefined workspace that enables you to monitor the performance of your mySAP instance, the operating system on which it runs, and the local area network (LAN) to which it is connected. By viewing the monitored operating system data in the Operating
51
System and LAN workspace, you can determine if there are external conditions affecting your mySAP application server performance. This workspace includes the following information: v CPU utilization v Load average v Memory configuration v Paging and swapping activity v LAN activity Additionally, the Monitoring Agent for mySAP provides a historical version of this workspace. You can request to view up to 24 hours of historical data for each component of this workspace. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transaction on the mySAP system: Operating System Monitor (ST06)
Output Requests workspace

Output Requests is a predefined workspace that contains the following specific information about output requests: v v v v v v v v v v v v Spool number and title Client Creator Print request time and minutes pending Output device and format Recipient Department Copies Size Number of print requests processed, in error, and failed Host spool ID Spooler system and host names
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Output Controller (SP01) v Display Spool Requests (SP02) v Sample Periods for ITM Reports
Refresh Database Statistics Results workspace

Refresh Database Statistics Results is a predefined workspace that provides status information on a request to refresh the database statistics. The expected information is that job RSORAT0D has been submitted in the mySAP system and that updated statistics will be available shortly. After reviewing the information in this workspace, return to the Database workspace to view the updated database statistics.
52
Reset Gateway Statistics Results workspace

Reset Gateway Statistics Results is a predefined workspace that provides status information on a request to reset gateway statistics. A message that indicates that the statistics were reset is displayed. Ensure that gateway statistics were reset. After seeing these results, you can return to the Gateway Statistics workspace to see the latest gateway statistics information.
SAP Office Inbox workspace

SAP Office Inbox is the default workspace for the SAP Office navigator group. SAP Office Inbox is a predefined workspace that contains the following SAP Office inbox statistics: v v v v Date and time the mail item was received Name of the user who currently owns a mail item Number of attachments included in the mail item Status of the mail item
Use this workspace to monitor SAP Office Inbox mail items. You can also ensure that important items are being processed in a timely manner. Each line in the SAP Office Inbox table links to the User Information workspace for the given User ID. All inbox items listed in the workspace have predefined Link options. You can use the link options to perform the following action: v Get User Information This option links to the User Information workspace, in which you can see detailed information about the user. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v SAPoffice Inbox (SO01) v Sample Periods for ITM Reports
SAProuter Log workspace

SAProuter Log is a predefined workspace that provides information about data in the mySAP router log file. You can use the SAProuter Log workspace to review log data pertaining to your mySAP system. You can use this information to see who is using the mySAP systems and from which IP address. Specifically, this workspace includes the following information: v Text from the SAPROUTER log file v Date and time recorded in the SAPROUTER log v Name of the mySAP system being monitored The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Sample Periods for ITM Reports v Log File Names for ITM Reports
53
Service Response Time workspace

Service Response Time is the default workspace for the Workload Performance navigator group. Service Response Time is a predefined workspace that provides diagnostics for each configured mySAP service running on the application instance you are monitoring. This workspace includes metrics for response time, wait time, CPU time, and database request time. For each configured mySAP service, this workspace provides the following information: v Metrics for minimum, maximum, and average response time v Metrics for minimum, maximum, and average wait time v Frequency of requests per minute for this service during the sample period The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03) v Sample Periods for ITM Reports
Spool Output workspace

Spool Output is a predefined workspace that provides information about all output requests for one spool request. This workspace includes the following information: v Spool number and title v Client v Creator v Print request time and minutes pending v Output device and format v Recipient v v v v v v Department Copies Size Number of print requests processed, in error, and failed Host spool ID Spooler system and host names
After reviewing the information in this workspace, return to the Spool Requests workspace to continue viewing other spool requests. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Output Controller (SP01) v Display Spool Requests (SP02) v Sample Periods for ITM Reports
Spool Requests workspace

Spool Requests is the default workspace for the Spool and Output navigator group. Spool Requests is a predefined workspace that provides information about spooling activity on the mySAP systems that you are monitoring, including associated output requests to designated devices and the following information: v Summary count of spool requests by output device v Summary count of spool requests by creator v Number and size of spool requests created
54
v Creator of the spool requests v Number of copies and the form required for printing v Print device selected for printing and the print status All spool requests listed in the workspace have predefined Link options. You can use the link options to perform the following action: v View output requests This link option opens the Spool Output workspace The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Output Controller (SP01) v Display Spool Requests (SP02) v Sample Periods for ITM Reports
Sub-Application Performance workspace

Sub-Application Performance is a predefined workspace that contains the following specific information about sub-application performance for each instance: v Application v Description v Number of dialog steps v Average and total response time, CPU time, wait time, and database request in milliseconds v Total database bytes requested in KB v Total number of database calls The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03) v Sample Periods for ITM Reports
System Log Detail workspace

System Log Detail is a predefined workspace that contains complete detailed information about a selected system log message. After viewing this detailed information, you can return to the System Log workspace to continue viewing other system log messages. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Online System Log Analysis (SM21) v Sample Periods for ITM Reports
System Log workspace

System Log is the default workspace for the Logs and Traces navigator group. System Log is a predefined workspace that provides the following detailed information about system log entries: v Type of task associated with the entry v Client and user activity that resulted in the log entry
55
v v v v
Transaction code associated with the entry Message information, such as number, class, and descriptive text Summary count of messages by message number Summary count of messages by message class
All messages listed in the workspace have predefined Link options. You can use the link options to perform the following action: v Get detailed message information This option links to the System Log Detail workspace, in which you can see all the detailed information about the syslog message. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Online System Log Analysis (SM21) v Sample Periods for ITM Reports
System Summary (agent level) workspace

System Summary (agent level) is the default workspace for the agent-level navigator node. This predefined workspace provides the following summary information about a mySAP system: v Configuration information about the mySAP system, including system ID, release level, database host, and central instance identity v Configuration information about each application server instance, including, hostname, instance number, start time, and number of work processes by type in each instance v Number of logged on users by instance Use this information in this workspace to guide you in examining the instances in this system.
System Summary (system level) workspace

System Summary (system level) is the default workspace for the System Summary navigator group. This predefined workspace provides information about the selected mySAP managed system that you are monitoring. Use this System Summary workspace to correlate data with information from associated workspaces so that you can efficiently evaluate key elements that can impact system performance throughout your mySAP enterprise. You can use this information to plan the following corrective actions: v Reconfigure application instances and associated mySAP services v Reconfigure the Operation Mode State for one or more instances v Reconfigure logon load balancing to more evenly distribute the user load between application servers
Transaction Performance workspace

Transaction Performance is a predefined workspace that contains the following specific information about all transactions for each instance: v Program or Tran code v Description v Dialog steps
56
v Average response time, CPU time, wait time, and database request time in milliseconds v Total response time, CPU time, wait time, database request time in milliseconds v Total bytes requested for databases in KB v Total number of database calls v Average extended memory and private memory in KB v Maximum extended memory per session and per tran in KB The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03) v Sample Periods for ITM Reports
Transactional RFC workspace

Transactional RFC is the default workspace for the Document Interchange navigator group. The Transactional RFC workspace provides information about data in the Transactional RFC file. This predefined workspace provides information that helps you determine the status of asynchronous Remote Function Calls. This workspace includes the following information: v Unique transaction identifier for the RFC v Logical target of the RFC v Size of the data to be transferred by the RFC v Number of retries allowed in attempting to connect to a specified system v Summary count of transactions by transaction code v Summary count of transactions by target system The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Asynchronous RFC Error Log (SM58) v Sample Periods for ITM Reports
Transport Log workspace

Transport Log is a predefined workspace that provides detailed log information about monitored transport steps. This workspace provides the following information: v Log file name v Display and error levels v Message numbers and message text After reviewing the information in this workspace, return to the Transport Objects and Steps workspace to continue reviewing other transport step logs. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Transport Organizer (SE10) v Sample Periods for ITM Reports
57
Transport Objects and Steps workspace

Transport Objects and Steps is a predefined workspace that shows the objects and steps for a given transport request. Because all transports contain objects, you always see information about transport objects. Transport step information is only available after the transport has been run. If you do not see transport step information, the transport might not have been run yet. This workspace contains the following specific information about transport objects: v v v v Object name Object type Object function Program ID
This workspace contains the following specific information about transport steps: v Target system v Step name v Return code v Execution time v Logfile name All transport steps listed in the workspace have predefined Link options. You can use the link options to perform the following actions: v View log This option links to the Transport Log workspace, allowing you to see detailed information about this transport step. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Transport Organizer (SE10) v Sample Periods for ITM Reports After reviewing the information in this workspace, return to the Transport Requests workspace to continue reviewing other transport requests.
Transport Requests workspace

Transport Requests is the default workspace for the Transport Requests navigator group. This predefined workspace provides detailed information about transport requests in the mySAP systems you are monitoring. You can use the Transport Requests workspace to monitor transport system activity occurring throughout your enterprise and learn specific details about each request. You can effectively audit changes to your development, test, and production systems. This workspace contains specific information about the request (for example, numeric identifier, and description), and its category (for example, customizing, repair, task, workbench, and so on). It also includes the following information: v User ID for the owner of the request v Date and time the request was most recently changed v Status of the request, such as documentation, locked, or released v Identifiers for the system and computer where the request originated v Identifiers for the systems and computers to which the requests have been imported
58
v Indicator for the highest return code for the request All transport requests listed in the workspace have predefined Link options. You can use the link options to perform the following action: v View transport objects and steps Use this link to open the Transport Objects and Steps workspace. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Transport Organizer (SE10) v Sample Periods for ITM Reports
User Information workspace

User Information is a predefined workspace that contains the following specific information for each user: v User ID v Client v Full name of user v Telephone number v v v v v v v Fax number Function Department Cost Center Country Building Room
After viewing the information in this workspace, return to your previous workspace to resume your normal work activities. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v User Maintenance (SU01) v Work Process Overview (SM50)
User Performance workspace

User Performance is a predefined workspace that contains the following specific information about application performance for each instance: v User ID v Description v Number of dialog steps v Average and total response time, CPU time, wait time, and database request in milliseconds v Total database bytes requested in KB v Total number of database calls The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03)
59
v Sample Periods for ITM Reports
User Transaction Performance workspace

User Transaction Performance is a predefined workspace that contains the following specific information about every unique combination of user ID and transaction or program name for each instance: v User ID v Program or Transaction code v Description v Dialog steps v Average response time, CPU time, wait time, and database request time in milliseconds v Total response time, CPU time, wait time, database request time in milliseconds v v v v Total bytes requested for databases in KB Total number of database calls Average extended memory and private memory in KB Maximum extended memory per session and per tran in KB
This workspace provides more specific information than the Transaction Performance or User Performance workspaces. The Transaction Performance workspace provides information about every transaction, but this information is aggregated across all users. The User Performance workspace provides information about every user, but this information is aggregated across all transactions. The User Transaction Performance workspace provides information about all users and all transactions, but aggregates only on the combination of user and transaction pair, hence providing greater granularity in the report. The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Performance, SAP Statistics, Workload (ST03) v Sample Periods for ITM Reports
Work Processes workspace

Work Processes is the default workspace for the Work Processes navigator group. This predefined workspace contains information about all mySAP work processes in this instance. You can use this workspace to review status and performance information for all defined work processes in this instance. This includes the following information: v Number of database reads v User ID of the person currently using a process v Total memory allocated to a specific process v Summary of work processes by type v Identification of long running work processes You can use the data for specific work processes for the following purposes: v Find out which processes are running, how long they have been running, and how many errors have occurred v Reduce the potential for bottlenecks and future trouble spots v Anticipate and plan for optimal performance on your mySAP system components
60
The workspace table view has predefined launch definitions. You can use the launch definitions to run the following transactions on the mySAP system: v Work Process Overview (SM50) v List of SAP Systems (SM51)
61
62
Chapter 5. Attributes reference

This chapter contains information about the following topics: v Overview of attributes v References for detailed information about attributes v Descriptions of the attributes for each attribute group included in this monitoring agent v Disk space requirements for historical data
About attributes
Attributes represent the detailed information about mySAP resources reported by the mySAP Agent. Attributes are organized by tables or attributes groups, where each attribute group is a collection of related attributes. This section provides a description of all attribute groups and the attributes they contain. The Monitoring Agent for mySAP has two types of attribute groups: Instance level Instance level attributes provide information about one mySAP application server or instance. System level System level attributes provide information about the mySAP system as a whole. These attributes are not specific to one application server or instance. Use attributes to create new queries to report only those attributes of interest and to create customized workspace views. The attributes you select in your queries appear as column headings in your table views. Use attributes to create new situations to monitor conditions of interest to you. Tailor the situations by specifying one or more attributes and their corresponding threshold values. Some of the attributes in this chapter are listed twice, with the second attribute having a (Unicode) designation after the attribute name. These Unicode attributes were created to provide access to globalized data. Use the globalized attribute names because this is where the monitoring agent is putting the data. If you were using a previous Candle OMEGAMON release of this monitoring agent, you must run the Application Migration Tool to create globalized attributes for your customized queries, situations, and policies. See the IBM Tivoli Monitoring Installation and Setup Guide for more information.
More information about attributes

For more information about using attributes and attribute groups, see theIBM Tivoli Monitoring Users Guide. For a list of the attribute groups, a list of the attributes in each attribute group, and descriptions of the attributes for this monitoring agent, refer to the Attribute groups and attributes section in this chapter.
63
Attribute groups and attributes

This monitoring agent contains the following attribute groups: v ABAP Dumps v Active Users v Alerts v Archive Monitor v Batch Data Create v Batch Data Create Log v Batch Jobs v Batch Job Logs v Buffer Performance v Data Base Detail v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v Data Base Summary Database Logs Developer Traces EDI Files File Systems Gateway Connections Gateway Statistics Instance Configuration Intermediate Documents Lock Entries Logon Group Number Range Buffer Details Number Range Buffer Summary Statistics Operating System Performance Output Requests Perform Requested Action SAP Office Inbox SAProuter Log Service Response Time Set Default Sample Period Spool Requests System Log System Log Details Topology Information Transaction Performance Transactional RFC Transport Log Transport Objects Transport Requests Transport Steps Updates Information User Information
64
v Work Processes The remaining sections of this chapter contain descriptions of these attribute groups, which are listed alphabetically. Each description contains a list of attributes in the attribute group.
ABAP Dumps attributes

ABAP Dumps is a system level attribute group. It provides information about ABAP short dumps occurring in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or name for the source client where the dump was created. Create Time The timestamp for the date and time the ABAP dump was created. Dump Title A text string identifier or name for the dump that was created. For example, DBIF RSQL INVALID CURSOR indicates the name of the dump. Hold Status The hold status for the dump, one of the following values: X = Held F = Free Host A text string identifier or name for the computer serving as the host where the dump was created. For example, ddrum2 indicates the name of the host where the dump was created. Include Name A text string identifier or name for the ABAP INCLUDE name. This attribute provides single-byte character support only. For example, LY210U58 indicates the ABAP INCLUDE name. Include Name (Unicode) A text string identifier or name for the ABAP INCLUDE name. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Line Number The numeric identifier for the line of code in the ABAP INCLUDE where the error occurred. For example, 750 indicates the line in the code where the error occurred. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Mode Number The dump mode number from view SNAP_BEG field MODNO, a text string. Program Name The text string identifier for the ABAP program that generated the dump. This attribute provides single-byte character support only. For example, SAPLY210 indicates the name of the ABAP program.
65
Program Name (Unicode) The text string identifier for the ABAP program that generated the dump. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Userid The text string identifier for the person who generated the dump. For example, LSMITH is the name of the person who generated the dump.
Active Users attributes

Active Users is an instance level attribute group. It provides information about users that are currently logged on to a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or name for the source client session. For example, 800 identifies the name of the client for this session. Echoed To Session The userid for a different user on this mySAP system. Use this text string attribute to identify sessions being echoed to other users SAPGUI screens for the purposes of monitoring, troubleshooting, or training personnel. For example, LBROWN identifies the name of the session echoed. External Sessions An integer value for the total number of external (true) sessions. For example, 2 specifies the total number of external sessions. Instance Name The name of the application instance you are monitoring. The valid format is a text string. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Internal Sessions An integer value for the total number of automatically opened internal sessions. For example, 3 specifies the total number of internal sessions. IP Address The IP address of the workstation running the SAPGUI presentation. This text string value is the same for all instances of a mySAP system. For example, 170.106.1.1 is the IP address for the database host in the mySAP system you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Sample Time The timestamp for the date and time the agent collected the data.
66
SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Session Number The identifier for the user session, a numeric value. For example, 2 is the number of the session. Session Time The timestamp for the date and time of the last session. Session Title The screen title of the session, a text string. For example, ABAP/4 Function Modules is the screen title of the session. This attribute provides single-byte character support only. Session Title (Unicode) The screen title of the session, a text string. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Terminal The hostname of the terminal running the SAPGUI presentation. Use this text string attribute to specify or exclude a specific terminal. For example, LBROWN is the name of the terminal being used. Time The timestamp for the time of the last user activity. Transaction Code The transaction code in which a users most recent activity took place. The code identifies each program that can be started from a menu in the mySAP system using a text string. For example, ST03 is the identifier for the mySAP transaction code. User Key The numeric identifier for the memory protection key for the user. For example, 216 is the name of the memory protection key for the user. User Page Size The page size, in KB, consumed by the user, a numeric value. For example, 16384 is the page size consumed by the user. User Private Memory The private memory, in KB, allocated to the user, a numeric value. For example, 34267 is the private memory allocated to the user. User Roll Size The roll size (where user memory is temporarily saved and retrieved from roll space), in KB, allocated to the user, a numeric value. For example, 11468 is the roll size allocated to the user. User Total Memory The total memory, in KB, consumed by the user, a numeric value. For example, 739313 is the total memory consumed by the user. Userid The name of the user logged on to this session, a text string. For example, LBROWN is the name of the person using this session.
Alerts attributes
Alerts is an instance level attribute group. It provides information about CCMS and mySAP Agent alerts occurring in a mySAP instance.
67
This attribute group can be used in queries, situations, and workspace views. CCMS alerts are similar to IBM Tivoli Monitoring situations in that they alert you to conditions in which a monitored valued has exceeded a threshold value. Alert Msg An alert message from the CCMS that provides more details on the reason for the alert. Alert Field Name The MTE attribute name, a text string. This attribute applies to CCMS alerts only. Alert Object Name The MTE object name, a text string. This attribute applies to CCMS alerts only. Alert Status The alert status, a number that indicates Open or Acknowledged. This attribute applies to CCMS alerts only. Alert Value The severity value from the CCMS. Class A category associated with an alert, as defined by mySAP. For example, DATABASE indicates that this alert involves database performance. Instance Name The name of the application instance you are monitoring, a text string. For example, DDRUM2_PRD_00. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message The text associated with an alert generated by mySAP. This attribute provides single-byte character support only. For example, NO BACKUPS ON RECORD indicates that no backup was detected. For CCMS alerts, this attribute contains a concatenation of all of the texts from the branches of the CCMS alert tree. This is the whole alert tree for the single alert in one attribute. Message (Unicode) The text associated with an alert generated by mySAP. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. For CCMS alerts, this attribute contains a concatenation of all of the texts from the branches of the CCMS alert tree. This is the whole alert tree for the single alert in one attribute. Monitor The CCMS Monitor to which this alert belongs, a text string. This attribute applies to CCMS alerts only. Monitor Set The CCMS Monitor Set to which this alert belongs, a text string. This attribute applies to CCMS alerts only. MTE Class A text string for the monitoring tree element in CCMS with which this alert is associated. Number A unique identifier assigned by the Monitoring Agent for mySAP that represents the alert type and subtype. Use this numeric value or range of values to identify or exclude an alert. For example, 517.
68
Occurrence Time The timestamp for the date and time that an alert or range of alerts occurred. See Alert timestamps on page 40 for detailed information about this timestamp. Occurrence Time GMT The time at which the alert occurred in Greenwich mean time. See Alert timestamps on page 40 for detailed information about this timestamp. Raised By The system that raised the alert, which is either the Monitoring Agent for mySAP or mySAP CCMS, a text string value that includes the following: S = mySAP C = Monitoring Agent for mySAP Sample Time The timestamp for the date and time the agent collected the data. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Severity A number that represents the level of severity used to identify or exclude a category of alert. The following values are possible: 0 = Normal (never reported by the Monitoring Agent for mySAP) 1 = Warning 2 = Critical System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Archive Monitor attributes

Archive Monitor is a system level attribute group. It provides information about document archiving occurring in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Archive Device Status The status of the archive device with values of OK or Missing, a text string. For example, OK indicates the archive device is operating properly. The following values are possible: 0 = OK 1 = Missing 2 = N/A Archiving Errors The number of errors that occurred during the archiving process. For example, 8 indicates the number of errors that occurred. Archiving Queues The number of queues that were generated during the archiving process. For example, 8 indicates the number of queues that were created. Background Archiving The number of background archiving jobs that are active. For example, 3 indicates the number of archiving jobs that are active in the background. Background Confirmation The number of background files that are confirmed. For example, 5 indicates the number of background files that are confirmed.
69
Background File Processing The number of background files processed. For example, 13 indicates the number of background files processed. Background Retrieval The number of background jobs retrieved. For example, 12 indicates the number of background jobs retrieved. Background Scheduled The number of background jobs scheduled. For example, 25 indicates the number of background jobs scheduled. Bar Code Archive Files The number of bar code archive files. For example, 152 indicates the number of bar code archive files. Confirmation Errors The number of archiving confirmation errors. For example, 15 indicates the number of archiving confirmation errors. Confirmation Queues The number of archiving confirmation queues. For example, 23 indicates the number of archiving confirmation queues. Logging Entries The number of logging entries. For example, 15 indicates the number of logging entries. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Open Asynchronous Errors The number of open asynchronous errors. For example, 6 indicates the number of open asynchronous errors. Open Asynchronous Requests The number of open asynchronous requests. For example, 9 indicates the number of open asynchronous requests. Open Bar Codes The number of open bar codes. For example, 7 indicates the number of open bar codes. Open Spool Errors The number of open spool errors. For example, 4 indicates the number of open spool errors. Open Spool Requests The number of open spool requests. For example, 7 indicates the number of open spool requests. Retrieval Errors The number of retrieval errors. For example, 6 indicates the number of retrieval errors. Retrieval Queues The number of retrieval queues. For example, 4 indicates the number of retrieval queues. Sample Time The timestamp for the date and time the agent collected data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
70
Transactional RFC Requests The number of transactional RFC spool requests. For example, 4 indicates the number of Transactional RFC spool requests.
Batch Data Create attributes

Batch Data Create (BDC) is a system level attribute group. It provides information about the configuration, progress, and performance of BDC sessions in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Authorization ID for the permission for the session, a text string. For example, RSMITH indicates the person who authorized the session. Client The name of the client session. For example, 800 identifies the source client for this session. Completed Screens The number of completed screens in this BDC session. For example, 21 indicates the number of screens that completed. Completed Transactions The number of completed transactions in this BDC session. For example, 35 indicates the number of transactions that completed. Created The timestamp for the date and time the BDC session or range of sessions occurred. Creator A text string identifier or user ID for the user who created the session. For example, RSMITH indicates the name of the person who created the session. Deleted Screens The number of deleted screens in this BDC session. For example, 3 indicates the number of screens that were deleted in this session. Deleted Transactions The number of deleted transactions in this BDC session. For example, 4 indicates the number of transactions that were deleted in this session. Error Screens The number of screens with errors. For example, 2 indicates the number of screens with errors. Error Transactions The number of transactions with errors. For example, 4 indicates the number of transactions with errors. Last Changed The timestamp for the date and time the session was most recently modified. Locked Until The timestamp for the specific date and time, or range, before which this session or a range of sessions cannot be processed. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Pending Screens The number of screens not yet completed in this BDC session. For example, 2 indicates the number of screens not yet completed.
71
Pending Transactions The number of transactions not yet completed in this BDC session. For example, 4 identifies the number of transactions not yet completed in this session. Queue Id The BDC queue Id from APQI-QID. Sample Interval End The timestamp for the specific date and time that the collection period stopped. Sample Interval Start The timestamp for the specific date and time that the collection period started. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Session Name A text string identifier or name for the BDC session. This attribute provides single-byte character support only. For example, RSMITH081358 indicates the name of the session. Session Name (Unicode) A text string identifier or name for the BDC session. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Start Mode The process used to begin the session. The following values are possible: A = Automatic M = Manual ? = Unknown Status The status for the session. The following values are possible: C = Being Created E = Errored F = Completed P = Pending R = Processing L = Locked ? = Unknown System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Total Screens The total number of screens in this BDC session. For example, 6 indicates the total number of screens for this session. Total Transactions The total number of transactions in this BDC session. For example, 67 identifies the number of transactions for this session.
Batch Data Create Log attributes

Batch Data Create Log is a system level attribute group. It provides log information for a particular Batch Data Create session. This attribute group can be used in queries, situations, and workspace views.
72
Created The timestamp for the date and time the BDC session was created. Execution Host A text string identifier or name for the computer serving as the execution host. For example, agoura1 indicates the name of the execution host. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Number A text string identifier or name for the system message. For example, S74 indicates the identifier for the system message. Message Text The descriptive text of the system message. This attribute provides single-byte character support only. For example, CONVERSATION ID: 53659 indicates the text of the system message. Message Text (Unicode) The descriptive text of the system message. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Message Time The timestamp for the date and time the message was logged into the BDC log. Queue Id The BDC queue Id from APQI-QID. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Screen Number A text string identifier or name for the transaction screen. For example, RSMITH081358 is the identifier for the transaction screen. Session Name A text string identifier or name for the BDC session. This attribute provides single-byte character support only. For example, RSMITH081358 indicates the identifier for the BDC session. Session Name (Unicode) A text string identifier or name for the BDC session. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Transaction A unique identifier for the transaction whose processing resulted in the log entry. This attribute provides single-byte character support only. For example, A309 indicates the identifier for the transaction. Transaction (Unicode) A unique identifier for the transaction whose processing resulted in the log entry. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment.
Batch Jobs attributes

Batch Jobs is a system level attribute group. It provides information about the configuration, progress, and performance of batch jobs in the mySAP system.
73
This attribute group can be used in queries, situations, and workspace views. Client An identifier for the execution client. For example, 800 indicates the identifier for the client. Defined By An identifier for the user who defined the batch job. For example, RSMITH specifies the user who defined the batch job. Definition Time The timestamp for the date and time the batch job was defined. Duration The calculated run time in minutes. End Time The timestamp for the date and time the batch job stopped. Execution Host The name of the computer serving as the execution host. For example, agoura1 is the name of the computer serving as the execution host. Job Class A category for the batch job. For example, A specifies the category of the batch job. Job Name A text string identifier or name for the batch job. This attribute provides single-byte character support only. For example, COLLECTOR FOR PERFORMANCE specifies the name of the batch job. Job Name (Unicode) A text string identifier or name for the batch job. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Job Number A numeric identifier for the batch job. For example, 11581001 identifies the number of a batch job. Last Changed By A text string identifier or user ID for the user who last modified the batch job. For example, SBROWN specifies the name of the user who last changed the batch job. Last Changed Time The timestamp for the date and time the batch job was most recently modified. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number of Steps The sum of the number of steps completed for this job. For example, 9 indicates the number of steps completed for this job. Other Scheduling Type A text string identifier for alternative types of scheduling. The following values are possible: E = Event J = AfterJob O = Opmode Other Scheduling Value A text string identifier for alternative scheduling values. For example, FIRST JOB indicates the jobname for an alternate scheduling type of AfterJob.
74
Periodic A text string indicator for how often the batch job is scheduled to run. For example, 02 HOURS indicates the job is scheduled to run every two hours. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data returned by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Scheduled Latest Time The timestamp for the date and time after which the job must not run. Scheduled Start Time The timestamp for the date and time the batch job is scheduled to begin. Start Time The date and time the batch job began. Status The status of the batch job. The following values are possible: A = Cancelled F = Finished P = Scheduled R = Active S = Released ? = Unknown System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Target Host An identifier or name for the computer designated as the target host.
Batch Job Logs attributes

Batch Job Logs is a system level attribute group. It provides log information about one batch job in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Job Name A text string identifier or name for the batch job. This attribute provides single-byte character support only. For example, COLLECTOR_FOR_PERFORMANCE specifies the name of the batch job. Job Name (Unicode) A text string identifier or name for the batch job. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Job Number A numeric identifier for the batch job. For example, 11581001 identifies the number of a batch job. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group.
75
Message Number A text string identifier or name for the system message. For example, S741 indicates the identifier for the system message. Message Number (610) Job log message number from TBTC5-MSGID and TBTC5-MSGNO through BP_JOBLOG_READ. This number consists of the message ID plus the message number. Message Text Descriptive text associated with the system message. This attribute provides single-byte character support only. For example, CONVERSATION ID: 53659 indicates the text of the system message. Message Text (Unicode) Descriptive text associated with the system message. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Message Time The timestamp for the date and time the message was logged into the job log. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Buffer Performance attributes

Buffer Performance is an instance level attribute group. It provides information about mySAP buffers and memory areas in one mySAP instance. This attribute group can be used in queries, situations, and workspace views. This attribute group contains a large number of attributes. Not all attributes apply to every object reported. When an attribute does not apply to a particular object type, the attribute has a value of -1. Changes The number of buffer updates. For example, 9 indicates the number of buffer updates. DB Access Quality (%) An indicator expressed as a percentage to indicate the percentage of requests that were satisfied from the buffer. This percentage must be close to 100%, and is calculated as (db_accesses_saved * 100) / (db_accesses + db_accesses_saved). For example, 99.37 indicates the percentage of requests that were satisfied. DB Accesses The number of times the database was accessed when the requested data was not available in the buffer. For example, 254 indicates the number of times the database was accessed. DB Accesses Saved The number of times the database accesses were saved. Database accesses occur when the requested data is not available in the buffer. For example, 57456 indicates the number of times the database accesses were saved. Deletes The number of buffer deletes. For example, 9 indicates the number of buffer deletes.
76
Directory Allocated The maximum number of objects that the buffer can hold, because one directory entry is required for each object that the buffer contains. For example, 12289 indicates the number of directory entries defined for a buffer. Directory Free The number of directory entries that are currently not in use, which is the number of new objects that can be added to this buffer if the buffer size is large enough. For example, 12140 indicates the number of directory entries not in use. Directory Free Percent The percentage of the directory that is free. Directory Used The number of directory entries that are currently in use, which is the number of objects currently in the buffer. For example, 149 indicates the number of directory entries currently in use. Directory Used Percent The percentage of the directory that was used. Encoded Name The encoded version of the Name attribute. The following values are possible: A = CALE B = CUA C = EIBUF D = ESM E = FTAB F = IRBD G = OTR H = PRES I = PXA J = SNTAB K = TABL L = TABLP M = TTAB N = MDH 1 = ExtendedMemory 2 = HeapMemory 3 = PageArea 4 = RollArea ? = Unknown Frames Swapped The number of frames swapped in the buffer. For example, 1 indicates the number of frames swapped in the buffer. Hitratio (%) An identifier, expressed as a percentage, indicating the percentage of requests that were satisfied from the buffer. The percentage is calculated (buffer_hits * 100) / buffer_requests), and must be close to 100%. For example, 99.37 indicates the percentage of requests that were satisfied from the buffer. Hits The number of times the requested data was available in the buffer. For example, 17268 indicates the number of times the data was available in the buffer.
77
Inserts The number of buffer inserts. For example, 28 indicates the number of buffer inserts. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Last Reset The timestamp for most recent date and time that the buffer was cleared out. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Max Used A numeric value metric specific to roll area, page area, heap, and extended memory. Max Used Percent A numeric value metric specific to roll area, page area, extended memory, and heap. Misses The number of times the requested data was not available in the buffer. For example, 468 indicates the number of times the requested data was not available in the buffer. Name A text string identifier or name for the buffer or memory area. For example, Heap memory indicates the name of a memory area and IRBD: Initial Records indicates the name of the buffer. Objects In Buffer The number of objects in the buffer. For example, 189 indicates the number of objects in the buffer. Objects Swapped The number of objects swapped in the buffer. For example, 3 indicates the number of objects swapped in the buffer. Requests The number of buffer requests. For example, 17417 indicates the number of buffer requests. Sample Time The timestamp for the date and time the agent collected data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Size Allocated (kb) The amount of space, in KB, allotted for the buffer. For example, 5859 indicates the amount of space allotted for the buffer. Size Free (kb) The amount of buffer space or memory area available, in KB. For example, 4836 indicates the amount of buffer space available. Size Free Percent The percentage free for buffers and memory areas such as roll, page, and extended memory. Size In Memory A memory size metric specific to roll area, page area, and extended memory.
78
Size On Disk A disk-size metric specific to roll area and page area. Size Reserved The size reserved by mySAP for internal buffer management. The value is Size Allocated minus Size Used and Size Free. Size Reserved Percent The percentage reserved by mySAP for internal buffer management. The value is Size Reserved divided by Size Allocated. Size Used (kb) The amount of buffer space used, in KB. Use this attribute to specify the amount of buffer space used. For example, 629 indicates the amount of buffer space used. Size Used Percent The percentage used for buffers and memory areas such as roll and page. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Total Resets The total number of times the buffer space was cleared out. Resets occur automatically during system initialization, as well as manually. For example, 9 indicates the number of times the buffer space was cleared out.
Data Base Detail attributes

Data Base Detail is a system level attribute group. It provides detailed information about an Oracle database used in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Analysis Time The timestamp for the date and time mySAP collected the sample based on a periodic sample schedule. Extents The number of reserved blocks of continuous storage. For example, 43 indicates the number of reserved blocks of continuous storage. Extents Change (per day) The number of changes in the reserved blocks of continuous storage per day. For example, 49 indicates the number of changes per day in the reserved blocks. Files The number of files in tablespace. For example, 236 indicates the number of files in tablespace. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. <Max> Next Extent (kb) The maximum size allowed for the next extent allocated. Maximum Free (kb) The maximum amount of free space, in KB, in the database object. For example, 3267656 indicates the maximum amount of free space for the database object. Minimum Free (kb) The minimum amount of free space, in KB, in the database object. For example, 3267656 indicates the minimum amount of free space for the database object.
79
Object Name A text string identifier or name for the database object. For example, REFERENCE indicates the name of the database object. Object Type The category of the database object, such as, table, index, tablespace, or database. For example, Database indicates the object type. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Size (kb) The defined space, in KB, of the database object. For example, 52553 indicates the defined space of the database object. Size Change (per day) The amount of change, in KB, in the space used by the database during the last 24 hours. For example, 5893 indicates the amount of change in the space used by the database object. Size Free (kb) The amount of space available, in KB, for the database object. Use this attribute to specify the amount of space available for a database object. For example, 5255656 indicates the amount of space available for the database object. Size Free Percent The percentage of free space available for the database object. For example, 48 indicates the percentage of free space available for the database object. Size Used (kb) The amount of space, in KB, used by the database object. For example, 45986 indicates the amount of space used by the database object. Size Used Percent The percentage of space used by the database object. For example, 13 indicates the percentage of space used by the database object. Space Critical Indicates whether space for a database object has reached a critical stage during the last 24 hours. The following values are possible: 0 = No 1 = Yes Status The status of the database object, such as online, offline, or unknown. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Tables & Indices The number of tables and indices in tablespace. For example, 523 indicates the number of tables and indices in tablespace. Tables & Indices Change (per day) The number of tables and indices that have changed during the last 24 hours. For example, 23 indicates the number of tables and indices in table space that have changed per day. Used Change (per day) The amount of change, in KB, in the space used by the database object during the last 24 hours. For example, 78533 indicates the amount of space used per day by the database object.
Data Base Summary attributes

Data Base Summary is a system level attribute group. It provides summary information about an Oracle database used in the mySAP system.
80
This attribute group can be used in queries, situations, and workspace views. Analysis Time The timestamp for the date and time mySAP collected the sample based on a periodic sample schedule. Database A text string identifier or name for the database server. Use this attribute to specify the name of the database server. For example, ORACLE indicates the name of the database server. Freespace Problems The number of freespace problems. For example, 3 indicates the number of free space problems. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Minimum Free (kb) The minimum amount of free space, in KB, for the database object. For example, 1928 indicates the amount of free space for a database object. Missing In Database The number of objects unaccounted for in the database. Use this attribute to identify the number of objects unaccounted for. For example, 3 indicates the number of objects unaccounted for in the database. Missing In Dictionary The number of objects unaccounted for in the Oracle data dictionary. For example, 2 indicates the number of objects unaccounted for in the data dictionary. Name A text string identifier or name for the database instance. For example, CN1 indicates the name of the database instance. Object Type The category of the database object, such as, table, index, tablespace, or database. For example, Index indicates the type of database object. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Total Free (kb) The total amount of free space, in KB, for the database object. For example, 5090163 indicates the total amount of free space, in KB, for the database object. Total Free Percent The total amount of free space for the database object, expressed as a percentage. For example, 49 indicates the percentage amount of free space for the database object. Total Number The total number of database objects. For example, 13 indicates the total number of database objects. Total Size (kb) The total amount of space, in KB, for the database object. For example, 1045883 indicates the total amount of space for the database object. Total Used (kb) The total amount of space used, in KB, for the database object. For example, 5255653 indicates the amount of space used for the database object.
81
Total Used Percent The total amount of space used, expressed as a percentage, for the database object. For example, 51 indicates the percentage amount of space used for the database object.
Database Logs attributes

Database Logs is a system level attribute group. It provides information about database log files created in the mySAP system. This attribute group can be used in queries, situations, and workspace views. File Name The path and name of the database log file that you are monitoring. For example, K:\oracle\PRD\saparch\aczabeqq.SVE specifies the path and name of the database log file that you are monitoring. Log Data The text of the database log file that you are monitoring. For example, BRI01 Parameters is an example of text from the database log file. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Developer Traces attributes

Developer Traces is an instance level attribute group. It provides information about trace files created by a mySAP instance. This attribute group can be used in queries, situations, and workspace views. File Name The name of the trace file or the error file that you are monitoring. For example, dev_w0 is the name of the trace file that you are monitoring. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Log Data The text of the error message or the warning message from the trace file or the error file that you are monitoring. For example, ***enqueue Log File Process-Id=450*** is sample text of the error message from the error file. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group.
82
Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Component The code from the first character in each line, if applicable. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
EDI Files attributes

EDI Files is a system level attribute group. It provides information about electronic document interchange files used in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Delete File An indicator of whether the EDI file must be deleted after processing. The following values are possible: 0 = No 1 = Yes File Name The path and file name of the EDI file being processed. This attribute provides single-byte character support only. File Name (Unicode) The path and file name of the EDI file being processed. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Last IDOC The number of the IDOC within the file that was last processed successfully. For example, 4083 indicates the number of the IDOC within the file that was last processed. Last Record The number of the record within the file that was last processed successfully. For example, 108 indicates the number of the record within the file that was last processed. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Sample Time The timestamp for the date and time the agent collected data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
83
File Systems attributes

File Systems is an instance level attribute group. It provides information about file systems and directory structures used in a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Capacity (mb) The allocated size, in megabytes, of the file system. For example, 4083 indicates the allocated size of the file system. Full Forecast (days) The number of days the system estimates that it takes for the file system to become full based on calculations for increased usage during the last 24 hours. Note: This field only displays data when there is an increase in file system usage during the last 24 hours. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Descriptive text indicating the status of the file system. This attribute provides single-byte character support only. For example, Static indicates the status of the file system. The following values are possible: empty emptying rapidly emptying slowly filling rapidly filling slowly full static Message (Unicode) Descriptive text indicating the status of the file system. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. The following values are possible: empty emptying rapidly emptying slowly filling rapidly filling slowly full static Name A text string identifier or name for the file system. This attribute provides single-byte character support only. For example, L: indicates the name of the file system.
84
Name (Unicode) A text string identifier or name for the file system. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Time The timestamp for the date and time the agent collected data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Size Free (mb) The amount of space, in megabytes, available in the file system. For example, 108 indicates the amount of space available in the file system. Size Used (mb) The amount of space, in megabytes, used in the file system. For example, 3978 indicates the amount of space used in the file system. Size Used Percent The amount of space, expressed as a percentage, used in the file system. For example, 97 indicates the percentage of space used in the file system. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Gateway Connections attributes

Gateway Connections is an instance level attribute group. It provides information about the connections between a mySAP instance and external systems. This attribute group can be used in queries, situations, and workspace views. Connection Number The identifier for the connection number. For example, 6 specifies the connection number. Connection Speed The speed of the connection on your mySAP Gateway. The following values are possible: SLOW = slow connection FAST = fast connection For example, SLOW might specify the speed of a telephone line. FAST might indicate that a LAN connection is being used. Conversation Identifier The identifier for the connection conversation. For example, 862335 specifies the connection conversation number. CPIC Return Code The identifier for the last CPIC return code. For example, 0 indicates the identifier for the last return code. The last CPIC return code from structure GWY_CONNAT, field APPCRC, using function GWY_READ_CONNECTION_ATTRIBUTES. In Use Indicator of whether or not the connection is in use. The following values are possible: 0 = No 1 = Yes Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring.
85
Local APPC Version The identifier for the local APPC version. For example, 6 specifies Version 6 of the local APPC. Local Host The identifier for the name of the computer serving as the local host. For example, CAN2 is an example of a local host name. Local IP Address The local TCP/IP address. For example, 195.0.2.3 is an example of a local TCP/IP address. Local Logical Unit Name The identifier for the local logical unit. For example, drum2 is an example of a local logical unit name. Local Transaction Program Name The name of the local transaction program. For example, ksaagent is an example of a local transaction program name. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number of Connections The number of connections on your mySAP Gateway. For example, 14 specifies the number of connections. Registration Status The registration status for the system connection. For example, UNUSED specifies the registration status for the system connection. Remote APPC Version The version number for the remote APPC. For example, 6 specifies Version 6 of the remote APPC. Remote Host The identifier for the name of the computer serving as the remote host. For example, agoura1 is an example of a remote host name. Remote IP Address The identifier for the remote TCP/IP address. For example, 10.58.9.12 is an example of a remote TCP/IP address. Remote Logical Unit Name The identifier for the remote logical unit. For example, CAN2 is an example of a remote logical unit name. Remote Transaction Program Name The name of the remote transaction program. For example, sapdp00 is an example of a remote transaction program name. Request Time The timestamp for the time of the last request. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAP Return Code The last SAP return code from structure GWY_CONNAT, field SAPRC, using function GWY_READ_CONNECTION_ATTRIBUTES. For example, 0 indicates the identifier for the last SAP return code. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Status The status of the mySAP Gateway connection. For example, CONNECTED indicates the connection to the gateway is active.
86
Symbolic Destination Name The symbolic destination name. For example, sapgw00 indicates the symbolic destination name. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. System Type The type of the mySAP gateway client you are using. For example, LOCAL_R3 specifies the type of mySAP gateway client. Trace Level The trace detail level. For example, 0 specifies the trace level. Userid The name of the user making use of the connection. For example, RBROWN is the name of the user connected to the Gateway.
Gateway Statistics attributes

Gateway Statistics is an instance level attribute group. It provides performance and status information about gateway connections used by a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Gateway statistics are intended to be enabled for a short period of time during specific analysis. Enabling gateway statistics for a long period of time can result in the gateway statistics values becoming too large to report. Avg CPIC Read Time (msecs/read) The average CPIC read time, in milliseconds per read. For example, 47667 indicates the average CPIC read time, in milliseconds per read. Avg CPIC Write Time (msecs/write) The average CPIC write time, in milliseconds per write. For example, 23854 indicates the average CPIC write time, in milliseconds per write. Avg Reader Time (msecs/request) The average Gateway reader time, in milliseconds per request. For example, 28514 indicates the average Gateway reader time, in milliseconds per request. Avg TCP Read Time (msecs/read) The average TCP read time, in milliseconds per read. For example, 20482 indicates the average TCP read time, in milliseconds per read. Avg TCP Write Time (msecs/write) The average TCP write time, in milliseconds per write. For example, 18476 indicates the average TCP write time, in milliseconds per write. Avg Work Process Time (msecs/request) The average mySAP Gateway work process time, in milliseconds per request. For example, 18433 indicates the average mySAP Gateway work process time, in milliseconds per request. CMINITs The total number of CMINITs. For example, 2608 indicates the total number of CMINITs. Connect Accepts The number of accepted connections to the mySAP Gateway. For example, 52 indicates the total number of accepted connections.
87
Connection with Maximum Stack The number of the connection using the size of its maximum data stack. For example, 0 indicates the maximum data stack number of the connection. CPIC Errors The total number of CPIC errors. For example, 35 indicates the total number of CPIC errors. CPIC Read Rate (kb/sec) The CPIC read rate, in KB per second. For example, 13982 indicates the CPIC read rate, in KB per second. CPIC Read Size (bytes) The CPIC read size, in bytes. For example, 38947 indicates the CPIC read size, in bytes. CPIC Reads The total number of CPIC reads. For example, 3675 indicates the total number of CPIC reads. CPIC Write Rate (kb/sec) The CPIC write rate, in KB per second. For example, 478 indicates the CPIC write rate, in KB per second. CPIC Write Size (bytes) The CPIC write size, in bytes. For example, 38947 indicates the CPIC write size, in bytes. CPIC Writes The total number of CPIC writes. For example, 3675 indicates the total number of CPIC writes. Current Data Stack The size of the current data stack. For example, 0 indicates the size of the current data stack. Current Overflow Usage The size of the current overflow usage. For example, 0 indicates the size of the current overflow usage. Data Stack Limit The limit of the data stack size. For example, 30 indicates the limit of the data stack size. Fragmented TCP Reads The total number of fragmented TCP reads. For example, 2329 indicates the total number of fragmented TCP reads. Fragmented TCP Writes The total number of fragmented TCP writes. For example, 1 indicates the total number of fragmented TCP writes. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters A reserved field for holding execution parameters for KSAR3. Longest Reader Request The identifier for the longest reader request. For example, F_RECEIVE specifies the longest reader request. Managed System The identifier for this mySAP esource. The valid format is a text string for a mySAP system, instance, or group. Max CPIC Read Time (msecs/read) The maximum CPIC read time, in milliseconds per read.
88
Max CPIC Write Time (msecs/write) The maximum CPIC write time, in milliseconds per write. For example, 47624 indicates the maximum CPIC write time, in milliseconds per write. Max Data Stack The maximum size of the data stack. For example, 3 indicates the limit of the data stack size. Max Overflow Usage The maximum size of the overflow usage. For example, 5 indicates the maximum size of the overflow usage. Max Reader Time (msecs/request) The maximum mySAP Gateway reader time, in milliseconds per request. For example, 28589600 indicates the maximum mySAP Gateway reader time, in milliseconds per request. Max TCP Read Time (msecs/read) The maximum TCP read time, in milliseconds per read. For example, 346000 indicates the maximum TCP read time, in milliseconds per read. Max TCP Write Time (msecs/write) The maximum TCP write time, in milliseconds per write. For example, 353300 indicates the maximum TCP write time, in milliseconds per write. Max Work Process Time (msecs/request) The maximum mySAP Gateway work process time, in milliseconds per request. For example, 2329 indicates the maximum mySAP Gateway work process time, in milliseconds per request. Min CPIC Read Time (msecs/read) The minimum CPIC read time, in milliseconds per read. For example, 1112 indicates the minimum CPIC read time, in milliseconds per read. Min CPIC Write Time (msecs/write) The minimum CPIC write time, in milliseconds per write. For example, 1374 indicates the minimum CPIC write time, in milliseconds per write. Min Reader Time (msecs/request) The minimum mySAP Gateway reader time, in milliseconds per request. For example, 1600 indicates the minimum mySAP Gateway reader time, in milliseconds per request. Min TCP Read Time (msecs/read) The minimum TCP read time, in milliseconds per read. For example, 346000 indicates the minimum TCP read time, in milliseconds per read. Min TCP Write Time (msecs/write) The minimum TCP write time, in milliseconds per write. For example, 400 indicates the minimum TCP write time, in milliseconds per write. Min Work Process Time (msecs/request) The minimum mySAP Gateway work process time, in milliseconds per request. For example, 478 indicates the minimum mySAP Gateway work process time, in milliseconds per request. Overflows The total number of overflows. For example, 47 indicates the total number of overflows. Reader Requests The total number of mySAP Gateway reader requests. For example, 597844 indicates the total number of mySAP Gateway reader requests.
89
Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Statistics Active Indicator of whether gateway statistics are active or not active. If not active, they are not available. The following values are possible: 0 = No 1 = Yes 3 = Values_too_large._Reset_gateway_statistics System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. TCP Errors The total number of TCP errors. For example, 4 indicates the total number of TCP errors. TCP Read Rate (kb/sec) The TCP read rate, in KB per second. For example, 1112 indicates the TCP read rate, in KB per second. TCP Read Size (bytes) The TCP read size, in bytes. For example, 28965243 indicates the TCP read size, in bytes. TCP Reads The total number of TCP reads. For example, 124175 indicates the total number of TCP reads. TCP Write Rate (kb/sec) The TCP write rate, in KB per second. For example, 1374 indicates the TCP write rate, in KB per second. TCP Write Size (bytes) The TCP write size, in bytes. For example, 28895498 indicates the TCP write size, in bytes. TCP Writes The total number of TCP writes. For example, 111173 indicates the total number of TCP writes. Timeouts The total number of timeouts. For example, 3 indicates the total number of timeouts. Total CPIC Read Time (secs) The total CPIC read time, in seconds, or one of the following values: -1 = NoData -2 = NumberTooLarge For example, 1397437 indicates the total CPIC read time, in seconds. Total CPIC Write Time (secs) The total CPIC write time, in seconds, or one of the following values: -1 = NoData -2 = NumberTooLarge For example, 20540175 indicates the total CPIC write time, in seconds. Total Reader Time (secs) The total reader time, in seconds, or one of the following values:
90
-1 = NoData -2 = NumberTooLarge For example, 170468058 indicates the total reader time, in seconds. Total TCP Read Time (secs) The total TCP read time, in seconds, or one of the following values: -1 = NoData -2 = NumberTooLarge For example, 25433236 indicates the total TCP read time, in seconds. Total TCP Write Time (secs) The total TCP write time, in seconds, or one of the following values: -1 = NoData -2 = NumberTooLarge For example, 320489 indicates the total TCP write time, in seconds. Total Work Process Time (secs) The total work process time, in seconds, or one of the following values: -1 = NoData -2 = NumberTooLarge For example, 170298487 indicates the total work process time, in seconds. Work Process Requests The total number of mySAP Gateway work process requests. For example, 47 indicates the total number of mySAP Gateway work process requests.
Instance Configuration attributes

Instance Configuration is both a system level and instance level attribute group. At the system level, it provides configuration information about the mySAP system and about each instance. At the instance level, it provides configuration information about one mySAP instance. This attribute group can be used in queries, situations, and workspace views. Active Users The current number of users logged on to this application instance. For example, 47 indicates the number of users currently logged on to the instance you are monitoring. Assigned Update Instance The name of the application server assigned to a specific update server. For example, Updinst_SY1_00 is the instance configured with the mySAP update service for this application instance. Batch Processes The number of batch processes running on this application instance. For example, 4 is the number of batch processes running in the mySAP system you are monitoring. Batch Queue The number of work requests in the Batch dispatch queue. Batch Service Configured A Yes/No switch to indicate if the batch service is configured. The following values are possible: 0 = No. The batch service is not configured.
91
1 = Yes. The batch service is configured. Central Instance A Yes/No switch to indicate if the application server is the central instance. This attribute can be useful when tailoring a situation. The following values are possible: 0 = No. The application server is not the central instance. 1 = Yes. The application server is the central instance. Central Instance Name The name of the central instance application server that is configured for this mySAP system. Configuration String The services mask, or string, for this application server. For example, DVEBMGS indicates that the following mySAP services are configured for this instance: D = Dialog V = Update (stands for Verbucher in German) E = Enqueue B = Background M = Message server G = SNA gateway S = Spool Database Host IP Address The IP address of the physical system on which the database instance resides. This value is the same for all instances of a mySAP system. For example, 170.106.1.1 is the IP address for the database host in the mySAP system you are monitoring. Database Host Name The name of the host computer running the database instance of a system. For example, DBhost is the name of the database host in the mySAP system you are monitoring. Database Name The name of the database instance defined for this mySAP system. This name is frequently the same as the mySAP , and is the same for each instance of a mySAP system. For example, DB4 is the name of the physical system on which the database server resides in the mySAP system you are monitoring. Dialog Processes The number of dialog processes running on this application instance. For example, 8 is the number of dialog processes running in the mySAP system you are monitoring. Dialog Queue The number of work requests in the Dialog dispatch queue. Dialog Service Configured A Yes/No switch to indicate if the dialog service is configured. The following values are possible: 0 = No. The dialog service is not configured. 1 = Yes. The dialog service is configured Enqueue Queue The number of work requests in the Enqueue dispatch queue. Enqueue Service Configured A Yes/No switch to indicate if the enqueue service is configured. The following values are possible: 0 = No. The message enqueue is not configured. 1 = Yes. The message enqueue is configured.
92
Gateway Service Configured A Yes/No switch to indicate if the gateway service is configured. The following values are possible: 0 = No. The gateway service is not configured. 1 = Yes. The gateway service is configured. Instance Down Duration The amount of time, in minutes, an application instance has been down. For example, 12 indicates that a particular instance has been down for 12 minutes. Instance Host IP Address The IP address of the physical system on which the application instance resides. For example, 170.106.1.11 is the IP address of the physical system on which the application instance you are monitoring resides. Instance Host Name The name of the physical system, without the domain, on which this application server resides. For example, Insthost is the name of the application instance you are monitoring. Instance Name The name of the application server. Instance Op Mode State The state in which the instance is included in the current operation mode of this application server. The following values are possible: 0 = Configured. The instance is included in an operation mode. 1 = Not configured. The instance is not included in an operation mode. 2 = Misconfigured. The instance was configured improperly. ? = Unknown Instance Start Time The timestamp for the date and time the application instance started. Instance Status The status of this application instance, either running or not running. The following values are possible: 0 = Not running 1 = Running Instance Stop Time The timestamp for the date and time the application instance stopped. Instance Up Duration The amount of time, in minutes, an application instance has been up in this system. For example, 12 indicates that a particular instance has been up for 12 minutes. Instances Down The total number of application instances that are down in this system. For example, 3 indicates that 3 instances you are monitoring are not running. Instances Running The total number of instances that are running in this system. For example, 15 indicates that 15 instances you are monitoring are running. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group.
93
Message Service Configured A Yes/No switch to indicate if the message server is configured. The following values are possible: 0 = No. The message service is not configured. 1 = Yes. The message service is configured. This instance is the central instance. NowP Queue The number of work requests in the NowP dispatch queue. Operation Mode A text string identifier or name for the current operation mode of the system. For example, Private indicates the current operation mode of the system. This attribute provides single-byte character support only. Operation Mode (Unicode) A text string identifier or name for the current operation mode of the system. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Spool Processes The number of spool processes running on this application instance. For example, 3 is the number of spool processes running in the mySAP system you are monitoring. Spool Queue The number of work requests in the Spool dispatch queue. Spool Service Configured A Yes/No switch to indicate if the spool service is configured. The following values are possible: 0 = No. The spool is not configured. 1 = Yes. The spool is configured. System Description A user-provided description of this application instance as defined in the mySAP system transport table. This attribute provides single-byte character support only. System Description (Unicode) A user-provided description of this application server instance as defined in the mySAP system transport table. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. System Number The number assigned to this application server instance. For example, 01 is the number of the mySAP instance you are monitoring. System Release The release number for the level of software installed on this application server. For example, 640 indicates the level of software installed in the SAP mySAP system you are monitoring. System Start Time The timestamp for the date and time the system started.
94
System Up Duration The amount of time, in minutes, that the system has been up. For example, 12 indicates that the system has been up for 12 minutes. Total External Sessions The total number of user sessions (GUI and RFC). Total GUI Sessions The total number of non-APPC-TM GUI sessions. Total RFC Sessions The total number of RFC sessions. Update Processes The number of update processes running on this application instance. For example, 2 is the number of update processes running in the mySAP system you are monitoring. Update Queue The number of work requests in the Update dispatch queue. Update2 Queue The number of work requests in the Update2 dispatch queue. Update Service Configured A Yes/No switch to indicate if the update service is configured. The following values are possible: 0 = No. The update service is not configured. 1 = Yes. The update service is configured.
Intermediate Documents attributes

Intermediate Documents is a system level attribute group. It provides information about documents transferred between this mySAP system and external systems. This attribute group can be used in queries, situations, and workspace views. Create Time The timestamp for the date and time the Intermediate Document (IDoc) was created. Direction The direction in which the IDoc transmission is being transmitted. The following values are possible: 1 = Outbound 2 = Inbound Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Code The logical message code, derived from an EDI message. This code further defines the type of message being transmitted. For example, 220 indicates that the message being transmitted is a purchase order. Message Function The logical message function in relation to its transmission. It contains a code derived from the message function of an EDI message. For example, TU indicates that the message transferred is a special invoice. Message Type The logical message type. This identification further defines the type of message being transmitted. For example, ORDERS indicates that the message type is a purchase order (outbound) or a sales order (inbound).
95
Number The identifying number for the IDoc. For example, 546 specifies the identifying number for the IDoc. Partner Function The function of the IDoc partner. For example, LF indicates that the partner is a vendor. Partner Name The name of the IDoc partner (for example vendor, customer, or a logical system). For example, LSYSTEM010 indicates the name of the partner. Partner Port The IDoc partner port, identifying the system that receives or sends IDocs. For example, RECEIVER indicates the port name of a receiver. Partner Type The IDoc partner type of receiver or sender. For example, KU indicates that the IDOC partner is a customer. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Status Description The IDoc status description, for example: Created or Translated. This attribute provides single-byte character support only. Status Description (Unicode) The IDoc status description. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Status for Statistics The IDoc statistical information. For example, InExternalSystem is the name of the mySAP system you are monitoring. 1 = Generated 2 = ReadyForDispatch 3 = InExternalSystem 4 = Dispatched 5 = ErrorsInInterface 6 = ErrorsInExternalSystem 7 = WithDeleteFlag B = TransferredToApplication C = TransferredToDialog D = Posted ? = Unknown Status Information The IDoc status information. This attribute provides single-byte character support only. For example, CREATED indicates that the IDoc has been created. Status Information (Unicode) The IDoc status information. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment.
96
Status Number The IDoc status number. For example, 02 indicates an error passing data to port. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Test Production Indicator of whether the message corresponding to the IDoc is a test message or a production message. The following values are possible: 1 = PROD 2 = TEST For example, TEST specifies that the IDoc is a test message. Type Defines the structure of the data associated with a message type. For example, DEBMAS02 for message type DEBMAS - customer master. This attribute provides single-byte character support only. Type (Unicode) Defines the structure of the data associated with a message type. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Update Time The timestamp for the date and time the Intermediate Document (IDoc) was updated.
Lock Entries attributes

Lock Entries is a system level attribute group. It provides information about locked objects in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Argument The argument value (key fields) of a lock entry. An entry locks the entries in a table that are specified by the argument value. For example, SAPLY210 is an example of an argument value. Backup Flag The identifier for the backup flag. For example, Y indicates that the backup flag is set. Client A text string identifier or number for the originating client. For example, 800 indicates the client. Create Time The timestamp for the date and time the lock was created Group The name of the group associated with the lock. For example, RZLLITAB indicates the name of the lock group. Hold Count The total number of locks held. For example, 1 indicates the total number of locks held. Host A text string identifier or name for the computer serving as the host. For example, agoura1 indicates the identifier for the host. Lock Age (mins) The amount of time, in minutes, elapsed since the lock was created. For example, 33 indicates the number of minutes elapsed since the lock was created.
97
Lock Object Name The name of the object being locked. For example, ES_RZL_LIP indicates the name of the object being locked. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Owner The name of the person associated with the lock. For example, LGREEN indicates the name of the person generating the lock. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. System Number The identifier for the mySAP system you are monitoring. For example, 06 is the identifier for the mySAP system you are monitoring. Transaction Code The identifier for the transaction code. For example, SMLG is the identifier for the transaction code. Update Hold Count The total number of locks held for update. For example, 2 indicates the total number of locks held for update. Update Owner The identifier for the person who holds the locks for update. For example, ddrum2..0002199901041 is the identifier for the person who holds the locks for update. Userid The name of the user who has set a lock. For example, RBROWN is the name of the user generating locks. Work Process The numeric identifier for the work process. For example, 3 is the number of the work process.
Logon Group attributes

Logon Groups is a system level attribute group. It provides information about the logon groups and server groups used to connect users to the instances in the mySAP system. This attribute group can be used in queries, situations, and workspace views Alternate IP Address The alternate IP address for this instance. For example, 10.21.1.11 is the name of the alternate IP address. Current Favorite The current favorite status for this instance in this logon group, which means this instance is picked for the next user that requests this logon group. For example, YES indicates that this instance is picked for the next user that requests this Logon group. The following values are possible: 0 = No 1 = Yes
98
Current Response Time The current response time, in milliseconds, for this instance. For example, 56 is the number of milliseconds it takes for responses. Current Users The current number of users on this instance. For example, 9 is the current number of users on this instance. Event Frequency (per/min) The number of events per minute on this instance. For example, 13 is the number of events per minute on this instance. Instance Name The name of the mySAP instance that is a member of this Logon/Server group. For example, ddrum2 PRD 00 is the name of the mySAP instance you are monitoring. Logon Parameters This attribute is reserved for internal use only. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Maximum Response Time (ms) The maximum allowed response time, in milliseconds, for this instance in this Logon group. For example, 0 is the maximum allowed response time for this instance in this group. Maximum Users The maximum allowed number of users in this Logon group on this instance. For example, 52 is the maximum allowed number of users in this Logon group on this instance. Name The name of the Logon/Server group that is assigned to a number of instances. Users are automatically logged on to the instance with the best response time. This attribute provides single-byte character support only. For example, ALL SERVERS is the name of the Server group you are monitoring. Name (Unicode) The name of the Logon/Server group that is assigned to a number of instances. Users are automatically logged on to the instance with the best response time. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Statistics Sample Time The timestamp for the date and time that the agent created these current statistics. Status The current instance status for this Logon/Server group. The following values are possible: 0 = Active 1 = Not Active System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Type The type of group that is being monitored. The following values are possible:
99
L = Logon S = Server
Logon Information attributes

Logon Information is a system level attribute group. It provides both current and historical information about users who have logged on to the mySAP system. This attribute group can be used in queries, situations, and workspace views. Client The name of the client to which you are logged on. For example, 800 is the name of the client you are logged on to. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Invalid Password Count The current number of invalid logons for this particular userid. For example, 3 indicates the current number of invalid logons for this particular userid. IP Address The IP address of the workstation being used. For example, 10.20.112.14 is the IP address for the workstation. Logon Logoff The action presently occurring at the workstation. The following values are possible: 0 = Logon Pending 1 = Logged On 2 = Invalid Logon 3 = Logged Off 9 = Current State For example, Logon Pending indicates that a user is presently logging on to the workstation. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Session Duration (mins) The duration of the logon session, in minutes, calculated from the logon time and the logoff time. For example, 22 indicates the duration of the logon session, in minutes. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
100
Terminal A text string identifier or name for the computer terminal where the user logged on to the mySAP system. For example, LBROWN indicates the computer terminal. Time The timestamp for the date and time of the logon, the logoff, or the failed logon. Userid The name of the user logging on to the session. For example, RBROWN is the name of the user initiating the session. Userid State The state of the user, either in a locked state or in a not locked state. The following values are possible: 0 = Not locked 1 = Locked Userid Type The type of user ID. The following values are possible: A = Dialog B = Batch C = CPIC D = BDC ? = Unknown
Number Range Buffer Details attributes

Number Range Buffer Details is an instance level attribute group. It provides information about the Number Range Buffer used in a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier, or number, for the originating client to which the number object applies. For example, 800 indicates the client system. External Range Indicator of whether a number range is externally assigned or internally assigned. The following values are possible: 0 = No. Internally assigned 1 = Yes. Externally assigned For example, NO indicates that number ranges are automatically assigned by the system. From Number The lowest number in this number range. For example, 000000000100 indicates the lowest number in this number range. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Interval To Number The highest number in this interval of this number range. For example, 0000000007699 indicates the highest number in this number range. Last Number The last number assigned in this number range. For example, 0000000007631 indicates the last number assigned in this number range. Logon Parameters A reserved field for holding execution parameters for KSAR3.
101
Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Object Name The name of this number object. For example, SPO_NUM is the name of this number object. Range Number The number associated with the number range. For example, 01 indicates the number associated with the number range. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Sub-object Name The name associated with the sub-object number. For example, NUM is the name of this sub-object. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. To Number The highest number in this number range. For example, 00000000032000 indicates the highest number in this number range. Year The year to which the number range applies. For example, 1998 indicates the year that the number range applies to.
Number Range Buffer Summary attributes

Number Range Buffer Summary is an instance level attribute group. It provides summary and statistical information about the Number Range Buffer used in a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Buffer Calls The total number of calls to the number range buffer. For example, 78 indicates the number of calls to the number range buffer. Buffer Responses Less Than 50us The total number of buffer responses less than 50 microseconds. For example, 54 indicates the number of buffer responses that are less than 50 microseconds. Buffer Responses Less Than 1ms The total number of buffer responses that are less than 1 millisecond and greater than or equal to 50 microseconds. For example, 26 indicates the number of buffer responses that are less than 1 millisecond and greater than or equal to 50 microseconds. Buffer Responses 1ms or Greater The total number of buffer responses that are 1 millisecond or greater. For example, 43 indicates the number of buffer responses that than 1 millisecond or greater. Buffer Size The allocated buffer size in KB. For example, 669354 indicates the number of KB allocated to the buffer. Conflicts The total number of number range buffer conflicts. For example, 6 indicates the number of number range buffer conflicts.
102
Current Entries The current number of entries in the number range buffer. For example, 43 indicates the current number of entries in the number range buffer. Current Indexes The current number of indexes in the number range buffer. For example, 12 indicates the current number of indexes in the number range buffer. Database Calls The number of calls to the database for number ranges. For example, 32 indicates the number of calls to the database for number ranges. Get Calls The number of get calls to the number range buffer. For example, 78 indicates the number of get calls to the number range buffer Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters A reserved field for holding execution parameters for KSAR3. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Maximum Entries The maximum number of entries in the number range buffer. For example, 1000 indicates the maximum number of entries in the number range buffer. Maximum Indexes The maximum number of indexes in the number range buffer. For example, 500 indicates the maximum number of indexes in the number range buffer. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Server Calls The number of calls to the server for the number range buffer. For example, 3 indicates the number of calls to the number range server. Server Responses Less Than 1 ms The total number of server responses less than 1 millisecond. For example, 26 indicates the number of server responses that are less than 1 millisecond. Server Responses Less Than 50 ms The total number of server responses less than or equal to50 milliseconds and greater than or equal to 1 millisecond. For example, 54 indicates the number of server responses that are less than 50 milliseconds and greater than or equal to 1 millisecond. Server Responses 50 ms or Greater The number of server responses that are 50 milliseconds or greater. For example, 22 indicates the number of server responses that are 50 milliseconds or greater. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Timeouts The number of timeouts to the number range buffer. For example, 3 indicates the number of timeouts to the number range buffer.
103
Operating System Performance attributes

Operating System Performance is an instance level attribute group. It provides information about the operating system on which a mySAP instance is running. This attribute group can be used in queries, situations, and workspace views. The SAP OS collector must be running on the mySAP instance for data to be returned for these attributes. Idle CPU Utilization (%) The amount of time the CPU is not processing instructions, expressed as a percentage. For example, 93 indicates that the CPU is idle 93 percent of the time it is available. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. KB Paged In (sec) The number of KB paged in per second. KB Paged Out (sec) The number of KB paged out per second. LAN Collisions (sec) The number of times LAN packets could not be delivered because two nodes attempted to send data at the same time. For example, 2 indicates the number of times LAN packets could not be delivered because two nodes attempted to send data at the same time during the last second. LAN Errors (sec) The total number of errors on the LAN during the last second. For example, 2 indicates the total number of errors on the LAN. LAN Packets In (sec) The number of units, known as packets, that were transferred from the LAN to mySAP during the last second. For example, 2 indicates the number of packets transferred in per second. LAN Packets Out (sec) The number of units, known as packets, that were transferred from mySAP to the LAN during the last second. For example, 2 indicates the number of packets transferred out per second. Load Average Last Minute The average computing burden the system carried during the last 60 seconds. For example, 0.08 indicates the average computing burden the system carried. Load Average Last 5 Minutes The average computing burden the system carried during the last five minutes. For example, 0.09 indicates the average computing burden the system carried. Load Average Last 15 Minutes The load average during the last 15 minutes. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Pages In (sec) The number of pages read from disk to update memory references to pages that were not previously referenced during the last second. For example, 0 indicates that no pages were read from disk to update memory references.
104
Pages Out (sec) The number of modified pages written to disk during the last second. For example, 3 indicates the number of pages written to disk per second. Physical Memory (kb) The total amount of physical memory (RAM). For example, 131136 indicates the total amount of physical memory, in KB. Physical Memory Free (%) The percentage of physical memory (RAM) available. For example, 78 indicates that 78% of RAM is available on this instance. Physical Memory Free (kb) The amount of physical memory (RAM) available, in KB. For example, 68976 indicates that 67 MB of RAM are available on this instance. Sample Time The timestamp for the date and time the agent collected the data from mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Swap Space (kb) The total amount of swap space configured, in KB. For example, 205224 indicates the total amount of swap space configured, in KB. Swap Space Free (%) The percentage of swap space available. For example, 78 indicates that 78% of swap space is available on this instance. Swap Space Free (kb) The amount of swap space available, in KB. For example, 411452 indicates that 411 MB of swap space are available on this instance. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. System CPU Utilization (%) The percentage of CPU used by system services. User CPU Utilization (%) The percentage of CPU used by user tasks.
Output Requests attributes

Output Requests is a system level attribute group. It provides information about all output requests in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or name for the originating client. For example, A800 indicates the identifier for the originating client. Copies The number of copies requested. For example, 31 indicates the number of copies requested. Creator The User ID for the originator of the request. For example, RSMITH indicates the originator of the request. Department A text string identifier or name for the current department receiving the request. This attribute provides single-byte character support only. For example, DEV indicates the current department receiving the request.
105
Department (Unicode) A text string identifier or name for the current department receiving the request. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Error Print Requests The number of print requests with errors. For example, 3 indicates the number of print requests with errors. Failed Print Requests The number of print requests that did not complete. For example, 2 indicates the number of print requests that did not complete. Host Spool Id A text string identifier for the print host spooler. For example, CAN2 indicates the identifier for the host spooler. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Output Device A text string identifier or name for the current output device. This attribute provides single-byte character support only. For example, LP01 indicates the name of the output device. Output Device (Unicode) A text string identifier or name for the current output device. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Output Format A text string identifier for the current output format. This attribute provides single-byte character support only. For example, X_65_255 indicates the output format. Output Format (Unicode) A text string identifier for the current output format. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Print Pending Time (minutes) Time calculated for the pending output request. Print Reason The reason for the print request. The following values are possible: M = Manual request G = Print immediately A = Archive request ? = Unknown Print Request Time The timestamp for the date and time the print request was created. Print Status The status of a print request. The following values are possible: 1 = Scheduled 2 = Is_Printing 3 = Unknown_in_OMS 4 = Completed_(problem) 5 = WaitingInHost
106
7 = Printing 9 = Complete A = Printer_is_locked B = Waiting_for_output_formatter C = Being_processed D = On_hold_after_a_problem E = Printer_is_locked F = Waiting_for_suitable_layout_set G = Fatal_Error_during_Processing H = Output_device_unavailable I = Internal_error_when_printing J = Status_unknown K = Deleted L = Incorrect M = Frontend_unavailable N = Query_problems O = Transferred_by_Command_to_the_Host_Spool P = Sent_to_LPD Q = Sent_to_SAPlpd R = Sent_to_Host_Spool S = Sent_to_IPP_Through_Host_Spool T = Sent_via_Mail U = Sent_to_RFC_Through_Host_Spool V = Waiting_for_Transfer_from_Front_End W = Sent_to_Front_End X = Forwarded_by_host_spool Y = Being_sent_to_host_spooler Z = Waiting_in_host_spooler ? = Unknown< Processed Print Requests The number of processed print requests. For example, 2 indicates the number of processed print requests. Recipient A text string identifier or name for the current recipient of the request. For example, RBROWN indicates the name of the recipient for the request. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Size The amount of disk space or memory to which the request can spool. For example, 4056 indicates that 4 MB of disk space is available for the request.
107
Spool Number A numeric identifier for the spool file. For example, 31806 indicates the numeric identifier for the spool file. Spool Title A text identifier or name for the spool file. This attribute provides single-byte character support only. For example, PRINTA indicates the title of the spool file. Spool Title (Unicode) A text identifier or name for the spool file. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Spooler Host Name A text string identifier or name for the host where the spooler is running. For example, DDRUM2 indicates the name of the spooler host. Spooler System Name A text string identifier or name for the system where the spooler is running. For example, DDRUM2_PRD indicates the system where the spooler is running. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Perform Requested Action attributes

Perform Requested Action attributes are reserved for internal use only.
SAP Office Inbox attributes

SAP Office Inbox is a system level attribute group. It provides information about SAP office resources and mail in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Action Name The name of the mySAP action specified in the mail item, such as program name, function module, or transaction name. This attribute provides single-byte character support only. For example, Y_210_NOTIFY indicates the name of the action in progress. Action Name (Unicode) The name of the mySAP action specified in the mail item, such as program name, function module, or transaction name. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Action Type The type of mySAP action specified in the mail item, such as program, function module name, or transaction. This attribute provides single-byte character support only. For example, FUNCTION MODULE indicates the type of SAP Office action associated with the mail item. Action Type (Unicode) The type of mySAP action specified in the mail item, such as program, function module name, or transaction. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Attachment Type The type of mail item as specified by its file extension. For example, DOC, XLS, TXT, and so on. DOC indicates the type of mail item is a document type.
108
Attachments The number of attachments included with the mail item. For example, 3 indicates the three attachments are included with the mail item. Author The name of the user who created the mail item. For example, WBROWN indicates the name of the user. Changeable An indicator of whether a mail item is modifiable. The following values are possible: 0 = No 1 = Yes 2 = Author (by author only) Client A text string identifier, or number, for the execution client. For example, 800 indicates the client. Expiration Time The timestamp for the expiration date and time of the mail item. Express Indicator of whether the mail item is an Express mail type or not. The following values are possible: 0 = No 1 = Yes Inbox Pending Time (mins) The amount of time, in minutes, that the mail item spent in the inbox prior to being opened. For example, 1171 indicates that the mail item spent 1,171 minutes in the inbox before being opened. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Mail Name The name of the mail item. This attribute provides single-byte character support only. For example, NOTE indicates the name of the mail item. Mail Name (Unicode) The name of the mail item. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Mail Title The title of the mail item. This attribute provides single-byte character support only. For example, status for 930 indicates the title of the mail item. Mail Title (Unicode) The title of the mail item. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Mail Type The type of mail item in the inbox. For example, Office, Workflow, or Deadline. This attribute provides single-byte character support only. Workflow indicates the mail item is of the Workflow type. Mail Type (Unicode) The type of mail item in the inbox. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Open Time The timestamp for the date and time the mail item was opened and viewed.
109
Owner The user name of the person who currently owns the mail item. For example, LGREEN indicates the name of the person who owns the mail item. Priority The priority of the mail item (the higher the number, the higher the priority). For example, 9 indicates that the mail item is of a high priority. Received Time The timestamp for the date and time the mail item was received. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Sensitivity The sensitivity of the mail item. The following values are possible: P = Private F = Functional S = Standard C = Company confidential ? = Unknown Sent Time The timestamp for the date and time the mail item was sent. Size (bytes) The size, in bytes, of the mail item. For example, 1785 indicates the size of the mail item. Status The status of the mail item. The following values are possible: 1 = Opened 2 = Unopened System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. User Name The name of the user who owns the SAP Office inbox. For example, LEROY BROWN is the name of the user who owns the SAP Office inbox. Userid The identifier for the user who owns the SAP Office inbox. For example, LGREEN is the name of the user who owns the SAP Office inbox.
Saprouter Log attributes

Saprouter Log is a system level attribute group. It provides information about the SAP router service in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Date Time The timestamp for the date and time recorded in the SAP Router log file. File Name The name of the SAP Router log file that you are monitoring. For example, SAPROUTER.LOG is the name of the SAP Router log file name.
110
Log Data The text from the SAP Router log file that you are monitoring. For example, CONNECT FROM CO, Host 127.0.0.1 (local host) is data from the SAP Router log file. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Service Response Time attributes

Service Response is an instance level attribute group. It provides performance information about the services running in a mySAP instance. These services include batch, dialog, enqueue, gateway, message, spool, and update. This attribute group can be used in queries, situations, and workspace views. Avg CPU Time (ms) The average amount of time, in milliseconds, the CPU processed instructions for this transaction. For example, 60 indicates that the amount of time the CPU processed instructions for this transaction averaged 60 milliseconds during the sampling period. Avg Database Request Time (ms) The average amount of time, in milliseconds, the database processed this transaction. For example, 12 indicates that the amount of time elapsed to complete database requests for this transaction averaged 12 milliseconds during the sampling period. Avg Response Time (ms) The average amount of time, in milliseconds, elapsed to process a request for this mySAP service. For example, 121 indicates that the response time averaged 121 milliseconds during the sampling period. Avg Wait Time (%) The average amount of time, expressed as a percentage, an unprocessed dialog step waited in the queue for a free work process. For example, 10 indicates that the amount of time, expressed as a percentage, an unprocessed dialog step waited in the queue for an available work process averaged ten percent during the sampling period. Avg Wait Time (ms) The average amount of time, in milliseconds, an unprocessed dialog step waited in the queue for a free work process. For example, 5 indicates that the amount of time, in milliseconds, an unprocessed dialog step waited in the queue for a free work process averaged 5 milliseconds during the sampling period.
111
Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Max CPU Time (ms) The maximum amount of time, in milliseconds, the CPU processed instructions for this transaction. For example, 180 indicates that the maximum amount of time, in milliseconds, the CPU processed instructions for this transaction was 180 milliseconds during the sampling period. Max Database Request Time (ms) The maximum amount of time, in milliseconds, elapsed for the database to process this transaction. For example, 54 indicates that the maximum amount of time elapsed to complete database requests for this transaction was 54 milliseconds during the sampling period. Max Response Time (ms) The maximum amount of time, in milliseconds, elapsed to process a request for this mySAP service. For example, 203 indicates that the maximum amount of time elapsed to process a request for this mySAP service was 203 milliseconds during the sampling period. Max Wait Time (ms) The maximum amount of time, in milliseconds, an unprocessed dialog step waited in the queue for a free work process. For example, 7 indicates that the maximum amount of time an unprocessed dialog step waited in the queue for an available work process was 7 milliseconds during the sampling period. Min CPU Time (ms) The minimum amount of time, in milliseconds, the CPU processed instructions for this transaction. For example, 30 indicates that the minimum amount of time, in milliseconds, the CPU processed instructions for this transaction was 30 milliseconds during the sampling period. Min Database Request Time (ms) The minimum amount of time, in milliseconds, elapsed for the database to process this transaction. For example, 6 indicates that the minimum amount of time elapsed to complete database requests for this transaction was 6 milliseconds during the sampling period. Min Response Time (ms) The minimum amount of time, in milliseconds, elapsed to process a request for this mySAP service. For example, 8 indicates that the minimum amount of time elapsed to process a request for this mySAP service was 8 milliseconds during the sampling period. Min Wait Time (ms) The minimum amount of time, in milliseconds, an unprocessed dialog step waited in the queue for a free work process. For example, 1 indicates that the minimum amount of time an unprocessed dialog step waited in the queue for a free work process was 1 millisecond during the sampling period. Private Mode Entered A text string that indicates whether the private address mode was entered: 0 = No 1 = Yes
112
Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The starting time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Service Frequency The number of times per minute this service was requested during the sample period. For example, 3 indicates that this service was requested three times per minute during the sampling period. Service Type The mySAP service category including batch, dialog, enqueue, gateway, message, spool, and update. For example, Dialog indicates that you are monitoring the mySAP dialog service. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Set Default Sample Period attributes

Set Default Sample Period attributes are reserved for internal use only.
Spool Requests attributes

Spool Requests is a system level attribute group. It provides information about all spool requests in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Authorization An authority object indicating permission to view a spool request. For example, RSMITH in the profile indicates that the user has permission to view a spool request. Client The identifier or number for the originating client. For example, 800 indicates the client. Copies The number of copies requested. For example, 3 indicates the number of copies requested. Cover Page An indicator showing whether a cover page was requested. The following values are possible: N = NoCover D = PrinterDefault S = CoverPage ? = Unknown Create Time The timestamp for the date and time the request was created. Creator The User ID for the originator of the request. For example, RSMITH indicates the User ID for the originator of the request. Delete After Print An indicator showing whether to delete or keep the spool file after printing. The following values are possible: K = Keep
113
D = Delete ? = Unknown Delete Time The timestamp for the date and time after which the spool file can be deleted. Department A text string identifier or name for the current department receiving the output of the request. This attribute provides single-byte character support only. For example, PAYROLL indicates the name of the department receiving the output. Department (Unicode) A text string identifier or name for the current department receiving the output of the request. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Error Print Requests The total number of print requests with errors. For example, 1 indicates the number of print requests with errors. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Output Device A text string identifier or name for the output destination for the spool request. This attribute provides single-byte character support only. For example, LP01 indicates the output destination for the spool request. Output Device (Unicode) A text string identifier or name for the output destination for the spool request. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Output Format A text string identifier for the current output format. This attribute provides single-byte character support only. For example, X_65_255 indicates the current output format. Output Format (Unicode) A text string identifier for the current output format. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Processed Print Requests The total number of processed print requests. For example, 15 indicates the number of processed print requests. Recipient A text string identifier or name for the current recipient of the request. For example, RSMITH indicates the name of the current recipient of the request. Request Closed An indicator showing whether the spool file can be appended. The following values are possible: C = Closed O = Open Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP.
114
Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Size The size in number of pages available for the spool request. For example, 14638 indicates the number of pages available for the request. Spool Number A numeric identifier for the spool file. For example, 31808 indicates the numeric identifier for the spool file. Spool Title A text identifier or name for the spool file. For example, LISTISLP01RSMITH indicates the textual identifier of the spool file. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Total Print Requests The total number of print requests for this spool request. For example, 3 indicates the total number of print requests for this spool request.
System Log attributes

System Log is an instance level attribute group. It provides information about all messages written to the system log in a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or number for the originating client. Use this attribute to specify an identifier for a client. For example, 800 indicates the identifier for the originating client. Development Class The identifier for the development class. For example, STUW is the identifier for the development class. Entry Time The timestamp for the date and time the log entry was made. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Class A text string identifier or name for the category of the message. The following values are possible: K = SAP_Web_AS_Problem S = Operation_Trace T = Transaction_Problem W = Warning X = Miscellaneous
115
Message Number A text string identifier or name for the system message. For example, S74 indicates the identifier for the system message. Message Text Descriptive text associated with the system message. This attribute provides single-byte character support only. For example, CONVERSATION ID: 53659 indicates the text of the system message. Message Text (Unicode) Descriptive text associated with the system message. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Program Name A unique identifier or name for the ABAP program that was running. This attribute provides single-byte character support only. For example, SAPLY210 indicates the name of the ABAP program. Program Name (Unicode) A unique identifier or name for the ABAP program that was running. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Record Count Count of system messages of a certain category. Reserved for use in queries to count messages by varying criteria. Record Number The log record number. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Task Type A text string identifier for the type of task associated with the entry. For example, RD indicates the type of task associated with the entry. Terminal A text string identifier or name for the computer terminal where the user logged onto the mySAP system. For example, LBROWN indicates the computer terminal. Transaction Code A unique identifier for the transaction whose processing resulted in the log entry. For example, A309 indicates the identifier for the transaction. User A text string identifier or user ID for the user whose activities resulted in the log entry. For example, RSMITH indicates the user who generated the log entry.
System Log Details attributes

System Log Details is an instance level attribute group. It provides detailed information about one message in the System Log attribute group. This attribute group can be used in queries, situations, and workspace views.
116
Entry Time The timestamp for the date and time the log entry was made. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Description Descriptive text providing information about the system activity that resulted in the message. This attribute provides single-byte character support only. For example, Problem Class indicates the text of the system message. Message Description (Unicode) Descriptive text providing information about the system activity that resulted in the message. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Message Text Descriptive text associated with the system message. This attribute provides single-byte character support only. For example, CPIC return code 20 indicates a communication error. Message Text (Unicode) Descriptive text associated with the system message. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Record Number The log record number. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Topology Information attributes

The Topology Information attributes are reserved for internal use only.
Transaction Performance attributes

Transaction Performance is an instance level attribute group. It provides information about transaction response time and performance characteristics within a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Aggregation Field reserved for internal use. Application The name of the business application name or of the sub-application name. This attribute provides single-byte character support only. For example, FI01 is the name of the business application you are monitoring. Application (Unicode) The name of the business application name or of the sub-application name. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment.
117
Avg CPU Time (ms) The average amount of time, in milliseconds, the CPU processed instructions for this transaction. For example, 36 indicates that the amount of time the CPU processed instructions for this transaction averaged 36 milliseconds during the sampling period. Avg Database Request Time (ms) The average amount of time, in milliseconds, elapsed for the database to process this transaction. For example, 2 indicates that the amount of time elapsed to complete database requests for this transaction averaged 2 milliseconds during the sampling period. Avg Extended Memory (kb) The average amount of extended memory, in KB. For example, 132 indicates that the amount of extended memory averaged 132 KB during the sampling period. Avg Private Memory (kb) The average amount of private memory, in KB. For example, 2612 indicates that the average amount of private memory is 2612 KB during the sampling period. Avg Response Time (ms) The average amount of time, in milliseconds, elapsed to process this transaction. For example, 177 indicates that the amount of time elapsed to process this transaction averaged 177 milliseconds during the sampling period. Avg Total Memory (kb) The total amount of memory, in KB. For example, 5632 indicates that the total amount of memory is 5632 KB during the sampling period. Avg Wait Time (ms) The average amount of time, in milliseconds, an unprocessed transaction waited in the queue for a free work process. For example, 1 indicates that the amount of time an unprocessed transaction waited in the queue for a free work process averaged 1 millisecond during the sampling period. Description The program name, transaction code, business application, or user ID description. This attribute provides single-byte character support only. Description (Unicode) The program name, transaction code, business application, or user ID description. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Dialog Steps The number of dialog steps completed for this transaction. For example, 5 indicates that five dialog steps completed for this transaction during the sampling period. Dynpro Number The Dynpro number referenced in the SAPGUI session. Front End Network Time The number of milliseconds used in network communication. This is the GUI Time minus the application server processing time. GUI Count The number of roundtrip requests from a user workstation to the mySAP instance and back to the user workstation. GUI Time The number of milliseconds required to respond to a user SAPGUI request. This time is measured from when the user presses a key to send a request until the response is received.
118
Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters This attribute is reserved for internal use only. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Max Extended Memory Per Session (kb) The maximum amount of extended memory, in KB, per session. For example, 132 indicates that the maximum amount of extended memory was 132 KB per session during the sampling period. Max Extended Memory Per Transaction (kb) The maximum amount of extended memory, in KB, per transaction. For example, 2 indicates that the maximum amount of extended memory was 2 KB per transaction during the sampling period. Program or Tran Code A text string identifier for the program name or transaction code you are monitoring. This attribute provides single-byte character support only. For example, FB01 indicates that the transaction code called FB01 is the name of the transaction you are monitoring. Program or Tran Code (Unicode) A text string identifier for the program name or transaction code you are monitoring. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Total CPU Time (ms) The total amount of time, in milliseconds, that the CPU processed instructions for this transaction. For example, 180 indicates that the CPU processed instructions for this transaction for 180 milliseconds during the sampling period. Total Database Calls The total number of database calls completed for this transaction. For example, 15 indicates that the application instance made a total of 15 requests to the database for this transaction during the sampling period. Total Database Request Time (ms) The total amount of time, in milliseconds, elapsed for the database to process this transaction. For example, 12 indicates that the amount of time elapsed to complete database requests for this transaction totaled 12 milliseconds during the sampling period.
119
Total DB Requested Bytes (kb) The total number of bytes, in KB, requested from the database for this transaction. For example, 6144 indicates that a total of 6 MB were requested from the database for this transaction during the sampling period. Total Response Time (ms) The total amount of time, in milliseconds, elapsed to process this transaction. For example, 333300 indicates that the amount of elapsed time, in milliseconds, to process this transaction totaled 3333300 milliseconds during the sampling period. Total Wait Time (ms) The total amount of time, in milliseconds, an unprocessed transaction waited in the queue for a free work process. For example, 2 indicates that the amount of time, in milliseconds, an unprocessed transaction waited in the queue for a free work process totaled 2 milliseconds during the sampling period. Userid The name of the user performing the transaction. For example, RBROWN is the name of the user performing the transaction.
Transactional RFC attributes

Transactional RFC is a system level attribute group. It provides information about documents exchanged between external systems and this mySAP system. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or name for the source client session where the RFC rund. For example, 017 identifies the name of the client for this session. Data Size (kb) The size of the data, in KB, to be transferred by the RFC. For example, 43278 specifies the size of the data to be transferred. Function Module The name of the function module that processed the RFC. This attribute provides single-byte character support only. For example, INBOUND_IDOC_PROCESS is the name of the function module that processed the RFC. Function Module (Unicode) The name of the function module that processed the RFC. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Hostname A text string identifier, or name, for the system that processed the RFC. For example, agoura1 indicates the name of the host where the RFC was processed. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Program The name for the main program that processed the RFC. This attribute provides single-byte character support only. For example, RDBSEMAT is the name of the main program that processed the RFC. Program (Unicode) The name for the main program that processed the RFC. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment.
120
Retries The number of retries allowed in attempting to connect to a specified system. For example, 3 specifies the number of retries attempted to connect to a system. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Send Receive A choice to either send RFC information or receive RFC information. The following values are possible: 1 = Send 2 = Receive Status The current status of the RFC. This attribute provides single-byte character support only. For example, PROCESSED BY EXTERNAL SYSTEM is the current status of the RFC. Status (Unicode) The current status of the RFC. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Target Name The name of the logical target of the RFC. This attribute provides single-byte character support only. For example, SYS1 is the name of the logical target system for the RFC. Target Name (Unicode) The name of the logical target of the RFC. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Time The timestamp for the date and time of the RFC processing. Transaction Code The identifier for the transaction code that called the RFC. This attribute provides single-byte character support only. For example, BD10 is the name of the transaction code that called the RFC. Transaction Code (Unicode) The identifier for the transaction code that called the RFC. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Transaction Id The unique transaction identifier for the RFC. For example, OA150D025778678DFA989 is the name of the transaction identifier for the RFC. Userid The identifier for the person creating the RFC. For example, LBROWN is the name of the person creating the RFC.
121
Transport Log attributes

Transport Log is a system level attribute group. It provides detailed log information about one step in a completed transport request in the mySAP system. This attribute group can be used in workspace views only. Display Level The display level from the step log. Error Level Error level from the step log. The following values are possible: E = Error W = Warning ? = Unknown Logfile Name The name of the log file, which is created from the transport directory and step name. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Message Number Message number from step log. Message Text Message text from the step log. This attribute provides single-byte character support only. Message Text (Unicode) Message text from the step log. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Number The request number from E070-TRKORR. Number (610) The request number from E070-TRKORR. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Transport Objects attributes

Transport Objects is a system level attribute group. It provides information about the objects in a particular transport request in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number A numeric identifier for the transport request. For example, CANK9002 indicates an identifier for the transport request.
122
Number (610) A numeric identifier for the transport request. Object Function An activity to occur on the transported object. The following values are possible: D = Delete M = Recreate K = TableKeys ? = Unknown Object Name The name of the transported object. For example, SAPLY210 indicates an identifier for the name of the object. Object Type The type of the transported object, as defined by the Transport System. For example, REPO indicates the type of transported object. Program Id The transport process tool associated with this transported object. For example, R3TR indicates the transport process tool. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD.
Transport Requests attributes

Transport Requests is a system level attribute group. It provides information about all transport requests in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Category A text string identifier for the Workbench or Customizing category. Note: The Workbench category of requests is associated with changes to planning and business rules. Customizing requests can include modifications to ABAP code or function modules. This attribute provides single-byte character support only. For example, Workbench indicates the workbench category of request. Category (Unicode) A text string identifier for the Workbench or Customizing category. The Workbench category of requests is associated with changes to planning and business rules. Customizing requests can include modifications to ABAP code or function modules. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Description Descriptive text associated with the request. This attribute provides single-byte character support only. For example, Initial Test Transport describes the request. Description (Unicode) Descriptive text associated with the request. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Highest Return Code The highest step return code. Possible values include the following: 0 = Perfect
123
4 = Warning 8 = Error 12 = Severe error Import Clients A text string identifier for the target client to which the request has been imported. For example, 012 indicates an identifier for the target client. Import Systems A text string identifier for the target systems, or the systems to which the request has been imported. For example, CN1 indicates an identifier for the target system. Last Changed Time The timestamp for the date and time the request was most recently changed. Logon Parameters This attribute is reserved for internal use only. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number A text string identifier for the transport request. For example, CANKSAV300 indicates an identifier for the transport request. Number (610) A text string identifier for the transport request. Owner A text string identifier or user ID for the owner of the request. For example, RSMITH indicates the user ID for the owner of the request. Parent Number A text string identifier for the parent request. For example, CANKSAV300 indicates an identifier for the parent request. Parent Number (610) A text string identifier for the parent request. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Source Client A text string identifier for the source client where the request was created. For example, 800 indicates an identifier for the source client. Source System A text string identifier for the source system, or the system where the request was created. For example, PRD indicates an identifier for the source system. Status The status of the request. The following values are possible: A = LockedAll D = Modifiable L = Modifiable_Protected N = Released_with_Import_Protection_for_Repaired_Objects O = Release_Started
124
P = Protected R = Released ? = Unknown System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Type The category of the request. The following values are possible: A = Request B = Translation C = Relocation_of_Objects_Without_Package_Change D = Piece_List_for_Support_Package E = Relocation_of_Complete_Package F = Piece_List G = Piece_List_for_CTS_Project K = Workbench_Request L = Local M = Client_Transport_Request O = Relocation_of_Objects_with_Package_Change P = Piece_List_for_Upgrade Q = Customizing_Task R = Repair S = Development_Correction T = Transport_of_Copies U = Dummy W = Customizing_Request X = Unclassified_Task ? = Unknown
Transport Steps attributes

Transport Steps is a system level attribute group. It provides details about completed transport steps for a particular transport request in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Execution Time The timestamp for the time the transport step was run. Logfile Name The logfile name created from the transport number and from the step name. For example, CANE9000010.PRD indicates an identifier for the logfile. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number A numeric identifier for the transport request. For example, CANE9000010.PRD indicates an identifier for the transport request. Number (610) A numeric identifier for the transport request.
125
Return Code The identifier for the return code. For example, 3672 indicates an identifier for the return code. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Step Name The name of the step. For example, EXPORT indicates an identifier for the step. The following values are possible: A = ABAP_Dictionary_Activation B = Inactive_Import C = C_Correction_Release D = Import_Application_Defined_Objects E = Export e = Export_pre_processing F = C_Transport_Release f = Checks_at_Operating_System_Level G = Generation_of_Programs_and_Screens H = Import_ABAP_Dictionary_Objects I = Import K = R3trans_Shadow_Import L = Import_Request_Piece_List M = Matchcode_and_Enqueue_Activation m = Generate_Transport_Information_File O = Trace_SPAM P = Test_Import P = Request_waiting_for_QA_approval Q = QA_approval_given R = Method_Execution R = Copy_File_Between_Transport_Groups T = Import_Table_Contents U = Customizing-Import V = Check_Versions v = Create_Versions_After_Import W = Routing w = Create_Versions_Before_Import X = Export_application_defined_objects Y = Transport_Again_with_Merge_Request 0 = No-Transport-Steps > = Deleted_from_buffer < = Selection_for_Import | = Import_not_approved ) = Transferring_System ( = Continue:_Other_Transport_Group : = Other_Domain # = Change_ADO_Code_Page ? = Unknown_Step
126
System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Target System The name of the mySAP system for which the transport is destined. For example, SY1 is the name of the mySAP system that the transport is destined for.
Updates Information attributes

Updates Information is a system level attribute group. It provides information about updates to the database in the mySAP system. This attribute group can be used in queries, situations, and workspace views. Client A text string identifier or name, for the source client session. For example, 017 identifies the name of the client for this session. Error The type of error that occurred during an update. This attribute provides single-byte character support only. For example, 00671:ABAP/4 processor: POSTING_ILLEGAL_STATEMENT indicates that an error occurred during the execution of a particular mySAP process. Error (Unicode) The type of error that occurred during an update. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Function Module The name of the function module associated with the update. For example, 03 indicates the name of the function module being used. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Program A text string identifier or name for the program that is performing the update. This attribute provides single-byte character support only. For example, SAPLY210 identifies the name of the program associated with this process. Program (Unicode) A text string identifier or name for the program that is performing the update. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Sample Interval End The timestamp for the stopping time of the data supplied by the Monitoring Agent for mySAP. Sample Interval Start The timestamp for the beginning time of the data supplied by the Monitoring Agent for mySAP. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. State Code The current state of the update. The following values are possible: 0 = OK 1 = V1 2 = V2
127
3 4 5 6 7
= Run = Del = Auto = Init = Err
State Description The description of the current state of the update. For example, Update is active indicates that an update is occurring. This attribute provides single-byte character support only. State Description (Unicode) The description of the current state of the update. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Status The current status of the update. The following values are possible: 0 = OK 1 = Initial 3 = Error Status Description Text describing the status of the update request. For example, Update is active indicates that the current update request is active. This attribute provides single-byte character support only. Status Description (Unicode) Text describing the status of the update request. For example, Update is active indicates that the current update request is active. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Status Number The identifier for the status. For example, 9 indicates the number of the update status. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Time The timestamp for the time the update was attempted. Transaction Code The identifier for the transaction code. For example, FB01 is the identifier for the transaction code you are using. Update Key The identifier for the update key. For example, 19991102131415000ddrum2...002 is the identifier of the update key. Update Server The name of the server being used for record updates. For example, ddrum2_PRD_00 is the identifier for the server you are using. Userid The name of the user performing the transaction. For example, RBROWN is the name of the user performing the transaction.
User Information attributes

User Information is an instance level attribute group. It provides detailed information about a particular user in the mySAP system. This attribute group can be used in queries, situations, and workspace views.
128
Building The number of the building in which the user works. For example, 1634 is the number of the building in which the user is located. This attribute provides single-byte character support only. Building (Unicode) The number of the building in which the user works. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Client The client identifier. For example, 800 is the name of the client. Cost Center The identifier for the cost center. This attribute provides single-byte character support only. For example, 5154 is the name of the cost center. Cost Center (Unicode) The identifier for the cost center. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Country The name of the country in which the user is located. This attribute provides single-byte character support only. For example, FRANCE Country (Unicode) The name of the country in which the user is located. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Department The name of the department associated with the user. This attribute provides single-byte character support only. For example, Apps.Dev. is the name of the department associated with this user. Department (Unicode) The name of the department associated with the user. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Fax Number The complete number (excluding the country code) of the Fax machine nearest to the user, including the extension of the number. For example, 8185551212 is the number of the Fax machine. Full Name The full name of the user, in local format. This attribute provides single-byte character support only. For example, Mike Brown is the full name of the user. Full Name (Unicode) The full name of the user, in local format. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Function The job function of the user. This attribute provides single-byte character support only. For example, SOFTWAREDEVELOPER is the job function of the user. Function (Unicode) The job function of the user. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group.
129
Room The identifier for the room in which the user is located. This attribute provides single-byte character support only. For example, 106A is the number of the room in which the user is located. Room (Unicode) The identifier for the room in which the user is located. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Telephone Number The complete number of the telephone assigned to the user (excluding the country code), but including the extension of the number. For example, 8185853382 is the telephone number of the user. Userid The name of the user performing the transaction. For example, RBROWN is the name of the user performing the transaction.
Work Processes attributes

Work Processes is an instance level attribute group. It provides information about all work processes running within a mySAP instance. This attribute group can be used in queries, situations, and workspace views. Action The current activity of the mySAP work process. The following values are possible: 5 = RollIn 6 = RollOut 7 = TXXX-Access 8 = TableLoad 10 = DirectRead 11 = SequentialRead 12 = PhysicalRead 13 = Insert 14 = Update 15 = Delete 16 = Commit 17 = Generate 18 19 20 28 29 31 32 33 34 = = = = = = = = = ReportLoad CUALoad DynPro QueueAPI DictionaryRead MatchcodeRead MatchcodeUpdate MatchcodeInsert PhysicalRead
130
35 = PhysicalUpdate 36 = PhysicalDelete 39 = MatchcodeDelete Client A text string identifier or name for the client in which the session is running. For example, 800 identifies the name of the client for this session. CPU Time (secs) The amount of time, in seconds, the CPU spent processing instructions for this mySAP process. For example, 10 indicates that the amount of time the CPU processed instructions for this mySAP process was 10 seconds during the sampling period. Database Changes The number of database changes, such as deletes, inserts, or updates, that occurred during the execution of a mySAP process. For example, 126 indicates that 126 database changes occurred during the execution of a particular process. Database Changes Time (ms) The amount of time it took, in milliseconds, to process database changes, such as deletes, inserts, or updates, during the execution of a mySAP process. For example, 374103 indicates that it took 374,103 milliseconds to process certain database changes during the execution of a particular mySAP process. Database Reads The number of database reads that occurred during the execution of an mySAP process. For example, 479 indicates that 479 database reads occurred during the execution of a particular process. Database Reads Time (ms) The amount of time it took, in milliseconds, to perform database reads during the execution of a mySAP process. For example, 1087655 indicates that it took 1,087,655 milliseconds to perform database reads during the execution of a particular mySAP process. Elapsed Time (secs) The amount of time, in seconds, that elapsed during the execution of the current request. For example, 59 indicates that 59 seconds elapsed during the execution of the current request. Errors The number of errors that occurred during the execution of a mySAP process. For example, 03 indicates that 3 errors occurred during the execution of a particular mySAP process. Instance Name The name of the application instance you are monitoring. For example, ddrum2_PRD_00 is the name of the application instance you are monitoring. Logon Parameters Parameters passed to ksar3 for any Take Action definition. Managed System The identifier for this mySAP resource. The valid format is a text string for a mySAP system, instance, or group. Number The identifier for the mySAP process. For example, 6 is the identifier for a particular mySAP work process. OS Process Id The identifier for the operating system process. For example, 5032 is the number of the operating system process.
131
Process Page Size (kb) The page size, in KB, consumed by the process. For example, 3 is the page size, in KB, consumed by the mySAP process. Process Private Memory (kb) The private memory, in KB, allocated to the process. For example, 42178 is the private memory, in KB, allocated to the mySAP process. Process Roll Size (kb) The roll size, in KB, consumed by the process. For example, 114688 is the roll size, in KB, consumed by the mySAP work process. Process Total Memory (kb) The total amount of private memory, in KB, allocated to the process. For example, 1011913 is the total amount of private memory, in KB, allocated to the mySAP work process. Program A text string identifier or name for the program that is currently executing in a work process. This attribute provides single-byte character support only. For example, SAPETHFB identifies the name of the program associated with this process. Program (Unicode) A text string identifier or name for the program that is currently executing in a work process. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Restart After Error A Yes/No switch that indicates whether a process must be restarted automatically after an abnormal termination during its execution. The following values are possible: 0 = No 1 = Yes Roll In-Out Count The number of roll in actions (where memory is retrieved from roll space), and roll out actions (where memory is temporarily saved to roll space) associated with this current user ID. For example, 127 is the number of roll ins and roll outs associated with this user. Roll In-Out Time (ms) The amount of time, in milliseconds, spent processing roll ins and roll outs for this mySAP process. For example, 261636 is the amount of time in milliseconds it took to process roll ins and roll outs for this mySAP process. Sample Time The timestamp for the date and time the agent collected the data. SAPshcut Parameters Parameters passed to sapshcut for any transaction launch definition. Status The current state of the work process. The following values are possible: 1 = Free 2 = Waiting - Waiting to execute a request 4 = Running - Executing a request 8 = Stopped - Waiting for an action to complete C = Complete ? = Unknown Status Reason The reason the process stopped. The following values are possible: 1 = Debug
132
2 3 4 5 6 7 8
= CPIC = ENQ = UPD = SPO = ADM = NUM = PRIV
? = Unknown System Name The SAP System Identifier (SID) for the mySAP system you are monitoring. For example, PRD. Table Name The name of the table currently being used by the work process. For example, TADIR is the name of the table currently being used. Transaction Code The identifier for the transaction code. This attribute provides single-byte character support only. For example, FB01 is a transaction code. Transaction Code (Unicode) The identifier for the transaction code. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Type The type of work process, such as dialog or batch. For example, UPD specifies a work process that runs dialog steps. The following values are possible: 0 = NWP 1 = DIA 2 = UPD 3 = ENQ 4 = BTC 5 = SPO 6 = UP2 7 = Unknown Userid The name of the person whose request is being processed. For example, LBROWN is the name of the person using this work process. Wait Information Information supplied by the mySAP system that explains why a process had to wait before executing. This attribute provides single-byte character support only. For example, CMRCV/6066760 is an example of wait information. Wait Information (Unicode) Information supplied by the mySAP system that explains why a process had to wait before executing. This attribute provides multi-byte character support. Use this attribute for new queries and situations to obtain worldwide language support in your environment. Wait Start Time The timestamp for the date and time the process started waiting to run.
133
Disk capacity planning for historical data

Disk capacity planning for a monitoring agent is a prediction of the amount of disk space to be consumed for each attribute group whose historical data is being collected. Required disk storage is an important factor to consider when you are defining data collection rules and your strategy for historical data collection. Calculate expected disk space consumption by multiplying the number of bytes per row by the expected number of rows, and then multiplying that product by the number of samples. Table 9 on page 135 provides the following information required to calculate disk space for the Monitoring Agent for mySAP attribute groups: v DB table name is the table name as it would appear in the warehouse database, if the attribute group is configured to be written to the warehouse. v Bytes per row (agent) is an estimate of the record length for each row written to the agent disk for historical data collection. This estimate can be used for agent disk space planning purposes. v Bytes per row (warehouse) is an estimate of the record length for detailed records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Detailed records are those that have been uploaded from the agent for long-term historical data collection. This estimate can be used for warehouse disk space planning purposes. v Bytes per summarized row (warehouse) is an estimate of the record length for aggregate records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Aggregate records are created by the Summarization agent for attribute groups that have been configured for summarization. This estimate can be used for warehouse disk space planning purposes. v Expected number of rows is a guideline that can be different for each attribute group, because it is the number of rows of data that the agent returns for a given attribute group, and depends upon the application environment that is being monitored. For example, if your attribute group is monitoring each processor on your machine and you have a dual processor machine, the number of rows is 2. Some attribute groups return mySAP system wide data. For these tables the Expected number of rows column indicates that the number of rows must be multiplied by each monitored mySAP system. Other tables return mySAP application server wide data. For these tables the Expected number of rows column indicates that the number of rows must be multiplied by each application server in each monitored mySAP System. For some tables, the Expected number of rows varies greatly between mySAP systems. In this case where there is no way to present a suitable guideline, the typical range for number of rows is specified. The maximum limit on the number of rows returned by the agent during a data collection is configurable. You can set it in the mySAP Configuration panel. See Maintain ITM generated alerts on page 22. The IBM Tivoli Monitoring Installation and Setup Guide IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can be used to estimate the amount of disk space used at the agent and in the warehouse database for historical data collection of an attribute group.
134
Table 9. Capacity planning for historical data Bytes per summarized row (warehouse) 1908 Expected number of rows Multiple, 1 row for each application server in each monitored mySAP System Multiple, 8 rows for each application server in each monitored mySAP System Multiple, 1 row for each CCMS alert that the agent is configured to report times the number of application servers in each monitored mySAP System Multiple, 1 row for each transaction, each user, each application, each subapplication, and each user transaction for each application server in each monitored mySAP system Multiple Multiple, 1 row for each job for each monitored mySAP system
Attribute group R/3_Instance_Configuration
DB table name KSASYS
Bytes per row (agent) 1135
Bytes per row (warehouse) 1091
R/3_Service_Response_Time
KSAPERF
544
565
848
R/3_Alerts
KSAALERTS
2280
2229
2266
R/3_Operating_System/ _Performance
KSAOSP
599
587
1440
R/3_Transaction_Performance R/3_Batch_Jobs
KSATRANS KSAJOBS
873 859
878 872
1422 963
135
Table 9. Capacity planning for historical data (continued) Bytes per summarized row (warehouse) 89 Expected number of rows Multiple, 1 row for each transport for each monitored mySAP system Multiple, 1 row for each object within each transport for each monitored mySAP system Multiple, 1 row for each step within each transports for each monitored mySAP system Multiple, 1 row for each spool that had activity in the sample period for each monitored mySAP system Multiple, 1 row for each output request that had activity in the sample period for each monitored mySAP system
Attribute group R/3_Transport_Requests
DB table name KSACTS 5
R/3_Transport_Objects
KSACTSOBJ
582
578
615
R/3_Transport_Steps
KSACTSSTEP
517
514
551
R/3_Spool_Requests
KSASPOOL
749
763
917
R/3_Output_Requests
KSAOUTPUT
976
992
1185
136
Table 9. Capacity planning for historical data (continued) Bytes per summarized row (warehouse) 977 Expected number of rows Multiple, 1 row for each file system in each application server in each monitored mySAP system Multiple, 17 rows for each application server in each monitored mySAP system Multiple, 1 row for each BDC session that had activity in the sample period for each monitored mySAP system Multiple, 4 rows for each monitored mySAP system Multiple, 1 row for each logged on user for each application server in each monitored mySAP system Multiple, 1 row for each work process (typically <100) for each application server in each monitored mySAP system
Attribute group R/3_File_Systems
DB table name KSAFSYSTEM
R/3_Buffer_Performance
KSABUFFER
631
679
1910
R/3_Batch_Data_Create
KSABDC
640
653
1080
R/3_Data_Base_Summary
KSAORASUM
504
508
896
R/3_Active_Users
KSAUSERS
749
759
1030
R/3_Work_Processes
KSAPROCESS
987
1008
1552
137
Table 9. Capacity planning for historical data (continued) Bytes per summarized row (warehouse) 903 Expected number of rows Multiple, 1 row for each dump that occurred during the sample period for each monitored mySAP system Multiple, 1 row for each lock (typically <1000) for each monitored mySAP system Multiple, 1 row for each update (typically <100) for each monitored mySAP system Multiple, 1 row for each RFC connection made to the gateway for each application server in each monitored mySAP system Multiple, 1 row for each application server in each monitored mySAP system
Attribute group R/3_ABAP_Dumps
DB table name KSADUMPS
R/3_Lock_Entries
KSALOCKS
689
696
850
R/3_Updates_Information
KSAUPDATES
1276
1286
1323
R/3_Gateway_Connections
KSAGWYCONN
1178
1194
1270
R/3_Number_Range_Buffer/ _Summary
KSANUMSUMM
587
536
1119
138
Table 9. Capacity planning for historical data (continued) Bytes per summarized row (warehouse) 604 Expected number of rows Multiple, 1 row for each number range (typically <100) for each application server in each monitored mySAP system Multiple, 1 row for each transactional RFC for each monitored mySAP system Multiple, 1 row for each logon group (typically <20) for each monitored mySAP system Multiple, row for each IDOC (typically > 1000) for each monitored mySAP system Multiple, 1 row for each EDI File (typically < 20) for each monitored mySAP system
Attribute group R/3_Number_Range_Buffer/ _Details
DB table name KSANUMDTL
R/3_Transactional_RFC
KSATRANRFC
1297
1319
1356
R/3_Logon_Groups
KSALOGNGRP
593
597
751
R/3_Intermediate_Documents
KSAIDOCS
1121
1133
1170
R/3_EDI_Files
KSAEDIFILE
848
848
885
139
Table 9. Capacity planning for historical data (continued) Bytes per summarized row (warehouse) 662 Expected number of rows Multiple, 1 row for each logon attempt or successful logon for each application server for each monitored mySAP system Multiple, 1 row for each monitored mySAP system Multiple, 1 row for each inbox entry for each monitored mySAP system
Attribute group R/3_Logon_Information
DB table name KSALOGNINF
R/3_Archive_Monitor
KSAARCHIVE
576
527
1110
R/3_SAP_Office_Inbox
KSAOFFICE
1233
1253
1329
For more information about historical data collection, see the IBM Tivoli Monitoring Administrators Guide.
140
Chapter 6. Situations reference

This chapter contains an overview of situations, references for detailed information about situations, and descriptions of the predefined situations included in this monitoring agent.
About situations
A situation is a logical expression involving one or more system conditions. Situations are used to monitor the condition of systems in your network. You can manage situations from the Tivoli Enterprise Portal by using the Situation editor. The IBM Tivoli Monitoring monitoring agents that you use to monitor your system environment are shipped with a set of predefined situations that you can use as-is or you can create new situations to meet your requirements. Predefined situations contain attributes that check for system conditions common to many enterprises. Using predefined situations can improve the speed with which you can begin using the Monitoring Agent for mySAP. You can examine and, if necessary, change the conditions or values being monitored by a predefined situation to those best suited to your enterprise. Note: The predefined situations provided with this monitoring agent are not read-only. Do not edit these situations and save over them. Software updates write over any of the changes that you make to these situations. Instead, copy the situations that you want to change to suit your enterprise. You can display predefined situations and create your own situations using the Situation editor. The left frame of the Situation editor initially lists the situations associated with the Navigator item that you selected. When you click a situation name or create a new situation, the right frame opens with the following tabs: Formula Condition being tested Distribution List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed. All of the Monitoring Agent for mySAP managed systems are assigned by default. Expert advice Comments and instructions to be read in the event workspace Action Command to be sent to the system Until Duration of the situation
More information about situations

The IBM Tivoli Monitoring Users Guide contains more information about predefined and custom situations and how to use them to respond to alerts.
141
For a list of the predefined situations for this monitoring agent and a description of each situation, refer to the Predefined situations section below and the information in that section for each individual situation.
Predefined situations
This monitoring agent contains the following predefined situations, which are organized by function: v ABAP Dump R3_ABAP_Dump R3_ABAP_Dump_Excessive v Active Users R3_USR_Echoed_Session R3_USR_Priv_Mode R3_USR_SAP_DDIC_online R3_USR_Security_Leak v Alert R3_Alert_Abort_Update_Crit R3_Alert_Crit R3_Alert_DB_Warn R3_Alert_No_Update_Crit R3_Alert_Output_Pending R3_Alert_Pend_Update_Crit R/3_Alert_System_Down R/3_Alert_Warn v Batch Data Create R3_BDC_Problem v Batch Jobs R3_Batch_Job_Warn R3_Batch_Too_Long R3_Batch_Too_Long_Crit R3_Batch_Too_Long_Warn R3_Delete_RunLong_Jobs v Buffer R3_Buffer_Directory_Crit R3_Buffer_Hitratio_Crit R3_Buffer_Hitratio_Warn R3_Buffer_Reset_Warn R3_Buffer_Swap_Crit SAP_Buffer_Quality_Crit SAP_Buffer_Quality_Warn SAP_Ext_Mem_Perc_Used_Crit SAP_Ext_Mem_Perc_Used_Warn SAP_Ext_Mem_Max_Perc_Used_Crit SAP_Ext_Mem_Max_Perc_Used_Warn SAP_Page_Max_Perc_Used_Crit
142
SAP_Page_Max_Perc_Used_Warn SAP_Roll_Max_Perc_Used_Crit SAP_Roll_Max_Perc_Used_Warn v Database R3_DB_Extents_Change_Warn R3_DB_Freespace_Problem R3_DB_Full_Crit R3_DB_Full_Warn R3_DB_Missing_Index_Problem R3_DB_Object_Space R3_DB_Objects_Freesize_Crit R3_DB_Objects_Freesize_Warn Delete R3_Delete_Old_BDC_Sessions R3_Delete_Old_Job_Logs R3_Delete_Old_Spool_Files Dialog R3_Dialog_Resp_Time_Crit R3_Dialog_Resp_Time_Warn R3_Dialog_Wait_Time_Crit R3_Dialog_Wait_Time_Warn Excess Memory R3_Excess_Memory_Warning File Systems R3_Filesystem_Fill_Fast_Crit R3_Filesystem_Fill_Fast_Warn R3_Filesystem_Full_Crit R3_Filesystem_Full_Warn R3_Filesystem_Too_Full Gateway Connections R3_GWY_Connection_with_error Instance Configuration R3_Inst_Down_PrimeTime R3_Instance_Down_Crit R3_Instance_Down2_Crit R3_Instance_Started Locks R3_Locks_Excessive R3_Locks_Long_Period Login and Logoff R3_LGN_Excessive_login_period R3_LGN_Invalid R3_LGRP_Inactive_Instance Number Range R3_NBUF_Performance_Crit
v v
v v
143
v OS and LAN R3_OS_CPU_Crit R3_OS_CPU_Warn R3_OS_LAN_Crit R3_OS_LAN_Warn R3_OS_Memory_Crit R3_OS_Memory_Warn R3_OS_Paging_Problem R3_OS_Swap_Space_Crit R3_OS_Swap_Space_Warn Output R3_Output_Pending_Problem R3_Printer_Locked R3_Printer_Problem R3_Printer_Unreachable_Warn Private Memory R3_Private_Memory_Critical Private Mode R3_Private_Mode_Crit Response Time R3_Average_Response_Time SAPGUI R3_Login_Slow R3_Main_Menue_Slow SAP Office R3_OFCE_Huge_msg SAP Router R3_ROUT_Problems Service Response R3_Buffer_Sync_Warn R3_Update_Resp_Time_Crit R3_Update_Resp_Time_Warn R3_Update_Wait_Time_Crit R3_Update_Wait_Time_Warn SAP_Batch_Resp_Time_Crit SAP_Batch_Resp_Time_Warn SAP_Spool_Resp_Time_Crit SAP_Spool_Resp_Time_Warn Spool R3_Spool_Aborted R3_Spool_Size_Crit R3_Spool_Size_Warn System Log R3_SYS_Abap_Dump R3_SYS_CPIC_Warn
v v v v
v v v
144
R3_SYS_DB_Warn R3_SYS_Trans_Rollback_Warn R3_SYS_Transaction_Warn SAP_Syslog_Crit SAP_Syslog_Warn v Transactional RFC R3_TRFC_problems v Transport R3_Transport_Crit R3_Transport_Repair_to_Prod R3_Transport_Repair_Warn R3_Transport_Warn v Updates R3_update_failure R3_update_failure_excessive v Work Processes R3_WP_CPU_High R3_WP_Error R3_WP_priv_mode R3_WP_Problem_Critical R3_WP_Restart The remaining sections of this chapter contain descriptions of each of these predefined situations. The situations are organized by function.
ABAP Dump situations

R3_ABAP_Dump notifies whether an ABAP dump was generated. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_ABAP_Dumps.Dump_Title NE
R3_ABAP_Dump_Excessive monitors for general excessive dumping problems. This situation is not activated at startup. This situation has the following formula:
IF COUNT R/3_ABAP_Dumps.Dump_Title GT 100
Active Users situations

R3_USR_Echoed_Session monitors for echoed sessions. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Active_Users.Echoed_To_Session NE
R3_USR_Priv_Mode monitors user interactions that force work processes into private mode. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Active_Users.User_Private_Memory GT 0
R3_USR_SAP_DDIC_online monitors to see if SAP* or DDIC super users are online in the system. This situation is not activated at startup. This situation has the following formula:
145
IF VALUE R/3_Active_Users.Userid EQ SAP* OR R/3_Active_Users.Userid EQ DDIC
R3_USR_Security_Leak monitors for potential security leaks. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Active_Users.Terminal EQ APPC-TM AND (VALUE R/3_Active_Users.Userid EQ SAP* OR VALUE R/3_Active_Users.Userid EQ DDIC)
Alert situations
R3_Alert_Abort_Update_Crit monitors terminated updates. This situation is activated at startup. This situation has the following formula:
IF VALUE R3_Alerts.Number EQ 9902
R3_Alert_Crit monitors mySAP critical alerts. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Alerts.Severity EQ Critical
R3_Alert_DB_Warn monitors database alerts. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Alerts.Class EQ Database
R3_Alert_No_Update_Crit monitors inactive updates. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Alerts.Number EQ 9901
R3_Alert_Output_Pending monitors pending output requests. This situation is not activated at startup. This situation has the following formula:
R3_Alert_Pend_Update_Crit monitors pending updates. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3__Alerts.Number EQ 9903
R/3_Alert_System_Down monitors mySAP system down. This situation is activated at startup. This situation has the following formula:
R/3_Alert_Warn monitors mySAP warning alerts. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Alerts.Severity EQ Warning
Batch Data Create situations

R3_BDC_Problem monitors Batch Data Create sessions that finished with errors. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Batch_Data_Create.Status EQ Errored
Batch Jobs situations

R3_Batch_Job_Warn monitors cancelled batch jobs. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Batch_Jobs.Status EQ Cancelled
146
R3_Batch_Too_Long monitors batch jobs running too long and cancels them if an error exists. This situation is associated with policy R3_Monitor_Batch_Jobs, and is not activated at startup. This situation has the following formula:
IF SIT (R3_Batch_Too_Long_Warn) EQ TRUE OR SIT (R3_Batch_Too_Long_Crit) EQ TRUE
R3_Batch_Too_Long_Crit monitors batch jobs running more than 5 hours. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Batch_Jobs.Duration GT 300
R3_Batch_Too_Long_Warn monitors batch jobs running more than 3 hours and less than 5 hours. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Batch_Jobs.Duration GT 180 AND VALUE R/3_Batch_Jobs.Duration LE 300
R3_Delete_RunLong_Jobs cancels long running jobs after 60 minutes. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Batch_Jobs.Status EQ Active AND VALUE R/3_Batch_Jobs.Duration GT 60
Buffer situations
R3_Buffer_Directory_Crit monitors no more free directory entries available. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Directory_Allocated NE 0 AND VALUE R/3_Buffer_Performance.Directory_Free EQ 0
R3_Buffer_Hitratio_Crit monitors buffer hit ratios below 90%. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Hitratio LT 90
R3_Buffer_Hitratio_Warn monitors buffer hit ratios that are above 90% and below 95%. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Hitratio LT 95 AND VALUE R/3_Buffer_Performance.Hitratio GE 90
R3_Buffer_Reset_Warn monitors for reset buffers. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Total_Resets GT 0
R3_Buffer_Swap_Crit monitors buffer objects that are swapped because of space problems. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Objects_Swapped GT 0
SAP_Buffer_Quality_Crit The database access quality for one of the buffers has fallen below the critical threshold. This situation is not activated at startup. This situation has the following formula:
147
IF VALUE R/3_Buffer_Performance.DB_Access_Quality LT 70.0 AND VALUE R/3_Buffer_Performance.DB_Access_Quality GE 0.0
SAP_Buffer_Quality_Warn The database access quality for one of the buffers has fallen below the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.DB_Access_Quality LT 90.0 AND VALUE R/3_Buffer_Performance.DB_Access_Quality GE 70.0
SAP_Ext_Mem_Perc_Used_Crit The percentage of extended memory in use has risen above the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ ExtendedMemory AND VALUE R/3_Buffer_Performance.Size_Used_Percent GT 95
SAP_Ext_Mem_Perc_Used_Warn The percentage of extended memory in use has risen above the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ ExtendedMemory AND VALUE R/3_Buffer_Performance.Size_Used_Percent LE 95 AND VALUE R/3_Buffer_Performance.Size_Used_Percent GT 75
SAP_Ext_Mem_Max_Perc_Used_Crit The maximum used percentage of extended memory has risen above the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ ExtendedMemory AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 95
SAP_Ext_Mem_Max_Perc_Used_Warn The maximum used percentage of extended memory has risen above the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ ExtendedMemory AND VALUE R/3_Buffer_Performance.Max_Used_Percent LE 95 AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 7
SAP_Page_Max_Perc_Used_Crit The maximum percentage of page memory in use has exceeded the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ RollArea AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 95
SAP_Page_Max_Perc_Used_Warn The maximum percentage of page memory in use has exceeded the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ PageArea AND VALUE R/3_Buffer_Performance.Max_Used_Percent LE 90 AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 70
148
SAP_Roll_Max_Perc_Used_Crit The percentage of roll area memory in use has risen above the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ RollArea AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 95
SAP_Roll_Max_Perc_Used_Warn The percentage of roll area memory in use has risen above the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Buffer_Performance.Encoded_Name EQ RollArea AND VALUE R/3_Buffer_Performance.Max_Used_Percent LE 95 AND VALUE R/3_Buffer_Performance.Max_Used_Percent GT 90
Database situations
R3_DB_Extents_Change_Warn monitors for changes in the number of extents. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Detail.Extents_Change_Per_Day GT 0
R3_DB_Freespace_Problem monitors for free space database problems. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Summary.Freespace_Problems GT 0
R3_DB_Full_Crit monitors space usage of database objects. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Summary.Total_Used_Percent GT 90
R3_DB_Full_Warn monitors space usage of database objects. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Summary.Total_Used_Percent GT 80 AND VALUE R/3_Data_Base_Summary.Total_Used_Percent LE 90
R3_DB_Missing_Index_Problem monitors for missing indexes. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Summary.Missing_In_Database GT 0 OR VALUE R/3_Data_Base_Summary.Missing_In_DDIC GT 0
R3_DB_Object_Space monitors critical space usage of database objects. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Detail.Space_Critical EQ YES
R3_DB_Objects_Freesize_Crit monitors free space of database objects. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Detail.Size_Free_Percent GE 0 AND VALUE R/3_Data_Base_Detail.Size_Free_Percent LT 8
R3_DB_Objects_Freesize_Warn monitors free space of database objects. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Data_Base_Detail.Size_Free_Percent GE 8 AND VALUE R/3_Data_Base_Detail.Size_Free_Percent LT 15
149
Delete Product-provided situations

R3_Delete_Old_BDC_Sessions Run RSBDCREO to delete obsolete BDC sessions/logs after 23:00. This situation is not activated at startup. This situation has the following formula:
IF VALUE Local_Time.Hours EQ 23
R3_Delete_Old_Job_Logs Run RSBTCDEL to delete obsolete job logs after 23:00. This situation is not activated at startup. This situation has the following formula:
R3_Delete_Old_Spool_Files Run RSPO0041 to delete obsolete spool files after 23:00. This situation is not activated at startup. This situation has the following formula:
Dialog situations
R3_Dialog_Resp_Time_Crit monitors response time of dialog work process. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Dialog AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 1500
R3_Dialog_Resp_Time_Warn monitors response time of dialog work process. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Dialog AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 1000 and VALUE R/3_Service_Response_Time.Avg_Response_Time LE 1500
R3_Dialog_Wait_Time_Crit monitors dialog wait time for CPU. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Dialog AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent GT 3
R3_Dialog_Wait_Time_Warn monitors dialog wait time for CPU. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Dialog AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent GT 1 AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent LE 3
Excess Memory situation

R3_Excess_Memory_Warning monitors for average total memory of more than 10 MB. This situation is not activated at startup. This situation has the following formula:
IF VALUE R3_Transaction_Performance.Avg_Total_Memory GE 10000
File Systems situations

R3_Filesystem_Fill_Fast_Crit monitors for file systems that are projected to reach capacity in less than one day. This situation is activated at startup. This situation has the following formula:
150
IF VALUE R/3_File_Systems.Full_Forecast GT 0 AND VALUE R/3_File_Systems.Full_Forecast LE 1
R3_Filesystem_Fill_Fast_Warn monitors for file systems that are projected to reach capacity in one to three days. This situation is not activated at startup.
IF VALUE R/3_File_Systems.Full_Forecast GT 1 AND VALUE R/3_File_Systems.Full_Forecast LE 3
R3_Filesystem_Full_Crit monitors for mySAP file system more than 90% full. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_File_Systems.Size_Used_Percent GT 90
R3_Filesystem_Full_Warn monitors for mySAP file system more than 80% full. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_File_Systems.Size_Used_Percent GT 80 AND VALUE R/3_File_Systems.Size_Used_Percent LE 90
R3_Filesystem_Too_Full monitors filling file system and takes action. This situation is associated with policy R3_Monitor_File_Systems, and is not activated at startup. This situation has the following formula:
IF SIT (R/3_Filesystem_Full_Warn) EQ TRUE OR SIT (R/3_Filesystem_Full_Crit) EQ TRUE
Gateway Connections situation

R3_GWY_Connection_with_error monitors for gateway connections that have CPIC/SAP errors. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Gateway_Connections.CPIC_Return_Code GT 0 OR VALUE R/3_Gateway_Connections.SAP_Return_Code GT 0
Instance Configuration situations

R3_Inst_Down_PrimeTime monitors for a mySAP instance down during prime time. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Instance_Configuration.Instance_Status NE Running AND VALUE Local_Time.Hours GE 08 AND VALUE Local_Time.Hours LE 18
R3_Instance_Down_Crit monitors for one instance down in a distributed (multi-instance) system. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Instance_Configuration.Instances_Running GT 0 AND VALUE R/3_Instance_Configuration.Instances_Down GT 0
R3_Instance_Down2_Crit monitors for one instance down in a multiple-instance system. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Instance_Configuration.Instance_Status EQ NotRunning
151
R3_Instance_Started monitors to see if an instance has started. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Instance_Configuration.Instance_Status EQ Running
Locks situations
R3_Locks_Excessive monitors for an excessive number of locks. This situation is not activated at startup. This situation has the following formula:
IF COUNT R/3_Lock_Entries.Lock_Object_Name GT 25
R3_Locks_Long_Period monitors for locks that have been on the system for a long time. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Lock_Entries.Lock_Age GT 60
Login and Logoff situations

R3_LGN_Excessive_login_period monitors to see if users are logged on too long. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Logon_Information.Terminal NE APPC-TM AND VALUE R/3_Logon_Information.Session_Duration GT 720
R3_LGN_Invalid monitors for invalid password entries. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Logon_Information.Invalid_Password_Count GE 1
R3_LGRP_Inactive_Instance monitors for inactive instances in a Logon Group. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Logon_Groups.Type EQ Logon AND VALUE R/3_Logon_Groups.Status EQ NotActive
Number Range situation

R3_NBUF_Performance_Crit monitors for number range buffer performance problems. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Number_Range_Buffer_Summary.Buffer_Responses_1ms_or_Greater GT 0
OS and LAN situations

R3_OS_CPU_Crit monitors for CPU usage over 85%. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Idle_CPU_Percent LT 15
R3_OS_CPU_Warn monitors for CPU usage over 70%. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Idle_CPU_Percent GE 15 AND VALUE R/3_Operating_System_Performance.Idle_CPU_Percent LT 30
R3_OS_LAN_Crit monitors for more than 5 LAN errors per second. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.LAN_Errors GT 5
152
R3_OS_LAN_Warn monitors for between 1 and 5 LAN errors per second. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.LAN_Errors GT 0 AND VALUE R/3_Operating_System_Performance.LAN_Errors LE 5
R3_OS_Memory_Crit monitors for free physical memory below 5%. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Physical_Memory_Free_Percent LT 5
R3_OS_Memory_Warn monitors for free physical memory below 10%. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Physical_Memory_Free_Percent LT 10 AND VALUE R/3_Operating_System_Performance.Physical_Memory_Free_Percent GE 5
R3_OS_Paging_Problem monitors for more than 10 pages per second paged out/in. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Pages_Out GT 10 OR VALUE R/3_Operating_System_Performance.Pages_In GT 10
R3_OS_Swap_Space_Crit monitors for free swap space below 5%. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Swap_Space_Free_Percent LE 5
R3_OS_Swap_Space_Warn monitors for swap space below 15%. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Operating_System_Performance.Swap_Space_Free_Percent LT 15 AND VALUE R/3_Operating_System_Performance.Swap_Space_Free_Percent GT 5
Output situations
R3_Output_Pending_Problem monitors for an output request pending for more than 60 minutes. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Output_Requests.Print_Status NE Complete AND VALUE R/3_Output_Requests.Print_Pending_Time GT 60
R3_Printer_Locked monitors for locked or disabled printer. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Output_Requests.Print_Status EQ PrinterLocked OR VALUE R/3_Output_Requests.Print_Status EQ PrinterDisabled
R3_Printer_Problem monitors for general output device errors. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Output_Requests.Print_Status EQ OutputDeviceError
R3_Printer_Unreachable_Warn monitors for printer destinations that are not reachable. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Output_Requests.Print_Status EQ ProblemWithConnection
153
Private Memory situation

R3_Private_Memory_Critical monitors for when the average private memory reaches a critical level. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Transaction_Performance.Avg_Private_Memory GT 0
Private Mode situation

R3_Private_Mode_Crit monitors for when work process enters private mode. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Private_Mode_Entered EQ Yes
Response Time situations

R3_Average_Response_Time monitors for an average response time of greater than 15 milliseconds. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Transaction_Performance.Avg_Response_Time GT 15
SAPGUI situations
R3_Login_Slow monitors SAPGUI login screen response time. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transaction_Performance.Program_or_Tran_Code EQ Login_Pw AND VALUE R/3_Transaction_Performance.Avg_Response_Time GT 50
R3_Main_Menue_Slow monitors SAPGUI main menu response time. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transaction_Performance.Program_or_Tran_Code EQ MainMenu AND VALUE R/3_Transaction_Performance.Avg_Response_Time GT 100
SAP Office situation

R3_OFCE_Huge_msg monitors for messages that are larger than 10 MB. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_SAP_Office_Inbox.Size GT 10000000
SAP Router situation

R3_ROUT_Problems provides an example of how to monitor for SAPROUTER problems. Modify the formula text string (Connection denied in this example) to match the Log_Data for which you are monitoring. This situation is not activated at startup. This situation has the following formula:
IF SCAN R/3_Saprouter_Log.Log_Data EQ Connection denied
Service Response situations

R3_Buffer_Sync_Warn monitors buffer synchronization. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ BufferSync AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 200
R3_Update_Resp_Time_Crit monitors response time of update work process. This situation is activated at startup. This situation has the following formula:
154
IF VALUE R/3_Service_Response_Time.Service_Type EQ Update AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 1000
R3_Update_Resp_Time_Warn monitors response time of update work process. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Update AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 700 AND VALUE R/3_Service_Response_Time.Avg_Response_Time LE 1000
R3_Update_Wait_Time_Crit monitors update wait time for CPU. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Update AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent GT 3
R3_Update_Wait_Time_Warn monitors update wait time for CPU. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Update AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent GT 1 AND VALUE R/3_Service_Response_Time.Avg_Wait_Percent LE 3
SAP_Batch_Resp_Time_Crit The average amount of time, in milliseconds, elapsed to process a request for this service has exceeded the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Batch AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 3000
SAP_Batch_Resp_Time_Warn The average amount of time, in milliseconds, to process a request for this service has exceeded the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Batch AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 1000 AND VALUE R/3_Service_Response_Time.Avg_Response_Time LE 3000
SAP_Spool_Resp_Time_Crit The average amount of time, in milliseconds, elapsed to process a request for this service has exceeded the critical threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Spool AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 3000
SAP_Spool_Resp_Time_Warn The average amount of time, in milliseconds, elapsed to process a request for this service has exceeded the warning threshold. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Service_Response_Time.Service_Type EQ Spool AND VALUE R/3_Service_Response_Time.Avg_Response_Time GT 1000 AND VALUE R/3_Service_Response_Time.Avg_Response_Time LE 3000
155
Spool situations
R3_Spool_Aborted monitors for spool requests that finish with an error. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Spool_Requests.Error_Print_Requests GT 0
R3_Spool_Size_Crit monitors for spool size that exceeds 1000 pages. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Spool_Requests.Size GT 1000
R3_Spool_Size_Warn monitors for spool size that exceeds 500 pages. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Spool_Requests.Size GT 500 AND VALUE R/3_Spool_Requests.Size LE 1000
System Log situations

R3_SYS_Abap_Dump monitors the mySAP system log for messages that an ABAP dump has been created. This situation is associated with policy R3_Monitor_ABAP_Dumps, and is activated at startup. This situation has the following formula:
IF VALUE R/3_System_Log.Message_Number EQ AB1
R3_SYS_CPIC_Warn monitors for a CPIC communications errors (R49, SA5). This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_System_Log.Message_Number EQ R49 OR VALUE R/3_System_Log.Message_Number EQ SA5
R3_SYS_DB_Warn monitors for Syslog database problems (BY*). This situation is not activated at startup. This situation has the following formula:
IF STR R/3_System_Log.Message_Number EQ 1,BY
R3_SYS_Trans_Rollback_Warn monitors for transaction rollbacks. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_System_Log.Message_Number EQ R68
R3_SYS_Transaction_Warn monitors for transaction runtime errors (AB0). This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_System_Log.Message_Number EQ AB0
SAP_Syslog_Crit monitors the mySAP system log for critical messages. Critical messages are specified by including the ID for the message in the situation formula. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_System_Log.Message_Number EQ A08 OR VALUE R/3_System_Log.Message_Number EQ GEG OR VALUE R/3_System_Log.Message_Number EQ R45
SAP_Syslog_Warn monitors the mySAP system log for warning messages. Warning messages are specified by including the ID for the message in the situation formula. This situation is not activated at startup. This situation has the following formula:
156
IF VALUE R/3_System_Log.Message_Number OR VALUE R/3_System_Log.Message_Number EQ OR VALUE R/3_System_Log.Message_Number EQ OR VALUE R/3_System_Log.Message_Number EQ OR VALUE R/3_System_Log.Message_Number EQ OR VALUE R/3_System_Log.Message_Number EQ OR VALUE R/3_System_Log.Message_Number EQ
EQ BZ7 EAS F7Y GI0 R0R R20 US4
Transactional RFC situation

R3_TRFC_problems provides an example of how to monitor for Transactional RFC problems. Modify the formula text string (Error in this example) to match the status text for which you are monitoring. This situation is not activated at startup. This situation has the following formula:
IF SCAN R/3_Transactional_RFC.Status EQ Error
Transport situations
R3_Transport_Crit monitors for transports with return codes greater than or equal to 12 (environmental problems). This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transport_Requests.Highest_Return_Code GE 12
R3_Transport_Repair_to_Prod monitors for repair transports imported into the production system. This situation is associated with policy R3_Production_Repairs and is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transport_Requests.Import Systems EQ PRD AND VALUE R/3_Transport_Requests.Type EQ Repair
R3_Transport_Repair_Warn monitors for repair transports. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transport_Requests.Type EQ Repair
R3_Transport_Warn monitors for transports with return codes 5 to 11. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Transport_Requests.Highest_Return_Code GT 4 AND VALUE R/3_Transport_Requests.Highest_Return_Code LT 12
Updates situations
R3_update_failure monitors for general update failures. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Updates_Information.Error NE
R3_update_failure_excessive monitors for excessive update problems. This situation is activated at startup. This situation has the following formula:
IF COUNT R/3_Updates_Information.Error GT 7
157
Work Processes situations

R3_WP_CPU_High monitors for high CPU usage by work process. This situation is not activated at startup. This situation has the following formula:
T
IF VALUE R/3_Work_Processes.CPU_Time GT 10
R3_WP_Error monitors for work process errors. This situation is activated at startup. This situation has the following formula:
IF VALUE R/3_Work_Processes.Errors GT 0
R3_WP_priv_mode monitors for work processes that are in private mode for reasons other than performance problems. This situation is activated at startup.
IF VALUE R/3_Work_Processes.Process_Private_Memory GT 0
R3_WP_Problem_Critical monitors the status of single work processes. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Work_Processes.Status EQ waiting OR VALUE R/3_Work_Processes.Status EQ stopped
R3_WP_Restart monitors for work processes that do not restart. This situation is not activated at startup. This situation has the following formula:
IF VALUE R/3_Work_Processes.Restart_After_Error EQ No
158
Chapter 7. Take Action commands reference

This chapter contains an overview of Take Action commands, references for detailed information about Take Action commands, and descriptions of the Take Action commands included in this monitoring agent.
About Take Action commands

Take Action commands can be run from the desktop or included in a situation or a policy. When included in a situation, the command runs when the situation becomes true. A Take Action command in a situation is also referred to as reflex automation. When you enable a Take Action command in a situation, you automate a response to system conditions. For example, you can use a Take Action command to send a command to restart a process on the managed system or to send a text message to a cell phone. Advanced automation uses policies to perform actions, schedule work, and automate manual tasks. A policy comprises a series of automated steps called activities that are connected to create a workflow. After an activity is completed, Tivoli Enterprise Portal receives return code feedback, and advanced automation logic responds with subsequent activities prescribed by the feedback.
More information about Take Action commands

For more information about working with Take Action commands, see the IBM Tivoli Monitoring Users Guide. For a list of the Take Action commands for this monitoring agent and a description of each command, refer to the Predefined Take Action commands section below and the information in that section for each individual command.
Predefined Take Action commands

This monitoring agent contains the following Take Action commands: v Alert Take Actions Close Alert v Batch Jobs Take Actions Cancel Job Delete Job Start Job v File Systems Take Actions Execute brarchive v Output Request Take Actions Output Request The remaining sections of this chapter contain descriptions of each of these Take Action commands, which are listed alphabetically.
159
The following information is provided about each Take Action command: Description Which actions the command performs on the system to which is it sent Arguments List of arguments, if any, for the Take Action with a short description. These are filled in automatically when the action runs within the context of a workspace table view that shows related attributes. For example, the Cancel Job arguments are automatically filled in when run from the Batch Jobs workspace. Destination systems Where the command is to be run: on the Managed System (monitoring agent) where the agent resides or on the Managing System (Tivoli Enterprise Monitoring Server) to which it is connected Usage Notes Additional notes relevant to using the task.
Cancel Job action

Description
While viewing the Batch Jobs workspace, you can cancel an active job on a mySAP system. This Take Action command invokes ksar3 on the monitoring agent to perform the action.
Arguments
This Take Action requires the following arguments, which are attributes from the R3_Batch_Jobs attribute group, to identify the job to be cancelled and to log on to the mySAP system: v Job_Name_U v Job Number v Logon Parameters
Destination systems
Managed system
Usage notes
This action can take a couple of minutes to complete. You receive one of the following return codes when you run this Take Action command: 0 Successful
non-zero Not successful. Check the task log for the given Take Action, or contact IBM Software Support.
Close Alert action

Description
While viewing the Alerts workspace, you can close a CCMS alert within a mySAP system. This take action command invokes ksar3 on the monitoring agent to perform the close.
160
Arguments
This Take Action requires the following arguments, which are attributes from the R3_Alerts attribute group, to identify the alert to be closed and to log on to the mySAP system: v Action v Logon Parameters
Destination systems
Managed system
Usage notes
Delete Job action

Description
While viewing the Batch Jobs workspace, you can delete a stopped job (Defined, Scheduled, Finished, and Cancelled) within a mySAP system. This Take Action command invokes ksar3 on the monitoring agent to perform the action.
Arguments
Destination systems
Managed system
Usage notes
Execute brarchive action

Description
While viewing any workspace, you can select the Execute brarchive action. This action causes the brarchive utility to offload the Database archive logs to tape. You can select the managed system on which to archive the logs to tape.
Arguments
There are no arguments for this Take Action command.
161
Destination systems
Managed system
Usage notes
Output Request action

Description
While viewing the Spool Requests, Spool Output, or Output Requests workspaces, you can create a new output request for a specific spool within the mySAP system. This Take Action command invokes ksar3 on the monitoring agent to perform the action.
Arguments
This Take Action requires the following arguments, which are attributes from the R/3_Spool_Requests attribute group, to identify the spool request for which an output request is to be created and to log on to the mySAP system: v Spool_Number v Logon_Parameters
Destination systems
Managed system
Usage notes
Start Job action

Description
While viewing the Batch Jobs workspace, you can start a scheduled job within a mySAP system. This action creates a copy of the job and immediately starts execution of the copy within mySAP. This Take Action command invokes ksar3 on the monitoring agent to perform the action.
Arguments
162
Destination systems
Managed system
Usage notes
163
164
Chapter 8. Policies reference

This chapter contains an overview of policies and references for detailed information about policies.
About policies
Policies are an advanced automation technique for implementing more complex workflow strategies than you can create through simple automation. A policy is a set of automated system processes that can perform actions, schedule work for users, or automate manual tasks. You use the Workflow Editor to design policies. You control the order in which the policy runs a series of automated steps, which are also called activities. Policies are connected to create a workflow. After an activity is completed, Tivoli Enterprise Portal receives return code feedback and advanced automation logic responds with subsequent activities prescribed by the feedback. Note: For monitoring agents that provide predefined policies, predefined policies are not read-only. Do not edit these policies and save over them. Software updates write over any of the changes that you make to these policies. Instead, copy the policies that you want to change to suit your enterprise.
More information about policies

For more information about working with policies, see the IBM Tivoli Monitoring Users Guide. For information about using the Workflow Editor, see the IBM Tivoli Monitoring Administrators Guide or the Tivoli Enterprise Portal online help.
Predefined policies
This monitoring agent contains the following predefined policies: v R3_Monitor_ABAP_Dumps v R3_Monitor_Batch_Jobs v R3_Monitor_File_Systems v R3_Monitor_Production_Repairs v R3_Start_Buffer_Monitoring The remaining sections of this chapter contain descriptions of each of these policies, which are listed alphabetically.
R3_Monitor_ABAP_Dumps
This policy monitors the mySAP system log for messages that an ABAP dump has been created. If these messages are issued each hour for 3 hours, you are offered a choice to run the ABAP program RSSNAPDL to delete and reorganize the ABAP Short Dumps, or wait 5 seconds and start monitoring again. You must create a variant for the RSSNAPDL program and replace the CUST_VAR value in the policy action with this variant name.
165
R3_Monitor_Batch_Jobs
This policy monitors executing batch jobs. When a job is running too long, you can either cancel the job, wait until the job run time is critically long, or wait 30 minutes and start monitoring again. If you choose to wait until the job run time is critically long, you can cancel the job at that time or wait 5 seconds and start monitoring again.
R3_Monitor_File_Systems
This policy monitors file system utilization. When a file system becomes too full, you can do one of the following: v Wait until the file system becomes critically full v Wait 5 seconds and start monitoring again v Run a cleanup script (or .bat file) v Run brarchive If you choose to wait until the file system is critically full, you are offered these same choices again. If you choose to run a cleanup script, you must provide the cleanup script. On Windows, the policy invokes a .bat file with a name of customer_cleanup.bat. On UNIX, the policy invokes a script file with a name of customer_cleanup.ksh.
R3_Monitor_Production_Repairs
This policy notifies you when a Repair Transport is imported into or created on the production system during Prime Shift. You must update the R3_Transport_Repair_to_Prod situation to replace the PRD value with the system identifier of your production system.
R3_Start_Buffer_Monitoring
This policy stops all buffer monitoring situations immediately after the mySAP instance has started. It restarts them 30 minutes later. The 30 minute delay is provided to allow the mySAP buffers time to reach a steady state, at which time buffer monitoring becomes meaningful.
166
Appendix A. IBM Tivoli Enterprise Console event mapping

Generic event mapping provides useful event class and attribute information for situations that do not have specific event mapping defined. Each event class corresponds to an attribute group in the monitoring agent. For a description of the event slots for each event class, see Table 10 on page 168. For more information about mapping attribute groups to event classes, see the IBM Tivoli Monitoring Administrators Guide. BAROC files are found on the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console event synchronization provides a collection of ready-to-use rule sets that you can deploy with minimal configuration. Be sure to install IBM Tivoli Enterprise Console event synchronization to access the correct Sentry.baroc, which is automatically included during base configuration of IBM Tivoli Enterprise Console rules if you indicate that you want to use an existing rulebase. See the IBM Tivoli Monitoring Installation and Setup Guide for details. Each of the event classes is a child of KSA_Base. The KSA_Base event class can be used for generic rules processing for any event from the Monitoring Agent for mySAP.
167
Table 10. Overview of event slots to event classes IBM Tivoli Enterprise Console event class ITM_R3_Instance_Configuration Event slots R/3_Instance_Configuration attribute group v managed_system: STRING; v instance_host_name: STRING; v system_release: STRING; v central_instance_name: STRING; v central_instance: STRING; v central_instance_enum: STRING; v database_name: STRING; v database_host_name: STRING; v message_service_configured: STRING; v message_service_configured_enum: STRING; v update_service_configured: STRING; v update_service_configured_enum: STRING; v dialog_service_configured: STRING; v dialog_service_configured_enum: STRING; v batch_service_configured: STRING; v batch_service_configured_enum: STRING; v enqueue_service_configured: STRING; v enqueue_service_configured_enum: STRING; v gateway_service_configured: STRING; v gateway_service_configured_enum: STRING; v spool_service_configured: STRING; v spool_service_configured_enum: STRING; v system_number: STRING; v instance_status: STRING; v instance_status_enum: STRING; v sample_time: STRING; v configuration_string: STRING; v instance_start_time: STRING; v system_start_time: STRING; v instance_stop_time: STRING; v active_users: INTEGER; v assigned_update_instance: STRING; v system_description: STRING; v database_host_ip_address: STRING; v instance_op_mode_state: STRING; v instance_op_mode_state_enum: STRING; v operation_mode: STRING; v dialog_processes: INTEGER; v update_processes: INTEGER; v batch_processes: INTEGER; v spool_processes: INTEGER;
168
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Instance_Configuration (continued) Event slots v instance_host_ip_address: STRING; v instances_running: INTEGER; v instances_down: INTEGER; v description: STRING; v ksa_value: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v system_up_duration: INTEGER; v system_up_duration_enum: STRING; v instance_up_duration: INTEGER; v instance_up_duration_enum: STRING; v instance_down_duration: INTEGER; v instance_down_duration_enum: STRING; v total_external_sessions: INTEGER; v total_external_sessions_enum: STRING; v total_gui_sessions: INTEGER; v total_gui_sessions_enum: STRING; v total_rfc_sessions: INTEGER; v total_rfc_sessions_enum: STRING; v nowp_queue: INTEGER; v nowp_queue_enum: STRING; v dialog_queue: INTEGER; v dialog_queue_enum: STRING; v update_queue: INTEGER; v update_queue_enum: STRING; v enqueue_queue: INTEGER; v enqueue_queue_enum: STRING; v batch_queue: INTEGER; v batch_queue_enum: STRING; v spool_queue: INTEGER; v spool_queue_enum: STRING; v update2_queue: INTEGER; v update2_queue_enum: STRING; v system_description_u: STRING; v operation_mode_u: STRING; v sapshcut_parameters: STRING;
169
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Service_Response_Time Event slots R/3_Service_Response_Time attribute group v managed_system: STRING; v service_type: STRING; v service_frequency: REAL; v private_mode_entered: STRING; v private_mode_entered_enum: STRING; v avg_wait_time: INTEGER; v avg_wait_percent: INTEGER; v avg_response_time: INTEGER; v max_response_time: INTEGER; v max_wait_time: INTEGER; v min_response_time: INTEGER; v min_wait_time: INTEGER; v avg_cpu_time: INTEGER; v max_cpu_time: INTEGER; v min_cpu_time: INTEGER; v avg_database_request_time: INTEGER; v max_database_request_time: INTEGER; v min_database_request_time: INTEGER; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v sapshcut_parameters: STRING;
170
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Alerts Event slots R/3_Alerts attribute group v managed_system: STRING; v ksa_class: STRING; v ksa_severity: INTEGER; v ksa_severity_enum: STRING; v occurrence_time: STRING; v message: STRING; v raised_by: STRING; v raised_by_enum: STRING; v sample_time: STRING; v number: INTEGER; v default_period: INTEGER; v logon_parameters: STRING; v logon_parameters_1: STRING; v logon_parameters_2: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v action: STRING; v mte_class: STRING; v alert_msg: STRING; v alert_object_name: STRING; v alert_field_name: STRING; v alert_value: INTEGER; v alert_value_enum: STRING; v alert_status: INTEGER; v alert_status_enum: STRING; v alert_unique_identifier: INTEGER; v alert_unique_identifier_enum: STRING; v monitor_set: STRING; v ksa_monitor: STRING; v occurrence_time_gmt: STRING; v action_l: STRING; v message_u: STRING; v sapshcut_parameters: STRING;
171
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Operating_System_Performance Event slots R/3_Operating_System_Performance attribute group v managed_system: STRING; v idle_cpu_percent: INTEGER; v idle_cpu_percent_enum: STRING; v physical_memory_free: INTEGER; v physical_memory_free_enum: STRING; v physical_memory_free_percent: INTEGER; v physical_memory_free_percent_enum: STRING; v swap_space_free: INTEGER; v swap_space_free_enum: STRING; v swap_space_free_percent: INTEGER; v swap_space_free_percent_enum: STRING; v load_average_last_minute: REAL; v load_average_last_5_minutes: REAL; v physical_memory: INTEGER; v physical_memory_enum: STRING; v swap_space: INTEGER; v swap_space_enum: STRING; v pages_in: INTEGER; v pages_in_enum: STRING; v pages_out: INTEGER; v pages_out_enum: STRING; v lan_packets_in: INTEGER; v lan_packets_in_enum: STRING; v lan_packets_out: INTEGER; v lan_packets_out_enum: STRING; v lan_collisions: INTEGER; v lan_collisions_enum: STRING; v lan_errors: INTEGER; v lan_errors_enum: STRING; v sample_time: STRING; v description: STRING; v ksa_value: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v load_average_last_15_minutes: REAL; v kb_paged_in: INTEGER; v kb_paged_in_enum: STRING; v kb_paged_out: INTEGER; v kb_paged_out_enum: STRING; v user_cpu_percent: INTEGER; v user_cpu_percent_enum: STRING;
172
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class TM_R3_Operating_System_Performance (continued) Event slots v system_cpu_percent: INTEGER; v system_cpu_percent_enum: STRING; v sapshcut_parameters: STRING; ITM_R3_Transaction_Performance R/3_Transaction_Performance attribute group v managed_system: STRING; v program_or_tran_code: STRING; v application: STRING; v userid: STRING; v description: STRING; v dialog_steps: INTEGER; v total_response_time: INTEGER; v avg_response_time: INTEGER; v total_cpu_time: INTEGER; v avg_cpu_time: INTEGER; v total_wait_time: INTEGER; v avg_wait_time: INTEGER; v total_database_request_time: INTEGER; v avg_database_request_time: INTEGER; v total_db_requested_bytes: INTEGER; v total_database_calls: INTEGER; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v aggregation: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v sapgui_hostname: STRING; v avg_total_memory: INTEGER; v avg_extended_memory: INTEGER; v max_extended_memory_per_session: INTEGER; v max_extended_memory_per_transaction: INTEGER; v avg_private_memory: INTEGER; v program_or_tran_code_u: STRING; v application_u: STRING; v description_u: STRING; v sapshcut_parameters: STRING; v dynpro_number: STRING; v gui_count: INTEGER; v gui_time: INTEGER; v front_end_network_time: INTEGER;
173
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Topology_Information Event slots R/3_Topology_Information attribute group v managed_system: STRING; v child_node: STRING; v parent_node: STRING; v instance_host_name: STRING; v configuration_string: STRING; v active_users: INTEGER; v server_type: STRING; v server_type_enum: STRING; v icon_label: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v icon_label_u: STRING; v sapshcut_parameters: STRING;
174
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Batch_Jobs Event slots R/3_Batch_Jobs attribute group v managed_system: STRING; v job_name: STRING; v job_number: INTEGER; v job_class: STRING; v job_class_enum: STRING; v client: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v target_host: STRING; v number_of_steps: INTEGER; v start_time: STRING; v end_time: STRING; v ksa_duration: INTEGER; v ksa_duration_enum: STRING; v definition_time: STRING; v defined_by: STRING; v last_changed_time: STRING; v last_changed_by: STRING; v scheduled_start_time: STRING; v scheduled_latest_time: STRING; v periodic: STRING; v other_scheduling_type: STRING; v other_scheduling_type_enum: STRING; v other_scheduling_value: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v execution_host: STRING; v job_name_u: STRING; v sapshcut_parameters: STRING;
175
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Batch_Job_Logs Event slots R/3_Batch_Job_Logs attribute group v managed_system: STRING; v job_name: STRING; v job_number: INTEGER; v message_time: STRING; v message_number: STRING; v message_text: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v message_text_u: STRING; v job_name_u: STRING; v sapshcut_parameters: STRING; v message_number_l: STRING; ITM_R3_Transport_Requests R/3_Transport_Requests attribute group v managed_system: STRING; v number: STRING; v type: STRING; v type_enum: STRING; v description: STRING; v owner: STRING; v last_changed_time: STRING; v category: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v parent_number: STRING; v source_system: STRING; v source_client: STRING; v import_systems: STRING; v import_clients: STRING; v highest_return_code: INTEGER; v highest_return_code_enum: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v number_l: STRING; v parent_number_l: STRING; v description_u: STRING; v category_u: STRING; v sapshcut_parameters: STRING;
176
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Transport_Objects Event slots R/3_Transport_Objects attribute group v managed_system: STRING; v number: STRING; v program_id: STRING; v object_type: STRING; v object_name: STRING; v object_function: STRING; v object_function_enum: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v number_l: STRING; v sapshcut_parameters: STRING; ITM_R3_Transport_Steps R/3_Transport_Steps attribute group v managed_system: STRING; v number: STRING; v target_system: STRING; v step_name: STRING; v step_name_enum: STRING; v return_code: INTEGER; v logfile_name: STRING; v execution_time: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v number_l: STRING; v sapshcut_parameters: STRING; ITM_R3_Transport_Logs R/3_Transport_Logs attribute group v managed_system: STRING; v number: STRING; v display_level: STRING; v error_level: STRING; v error_level_enum: STRING; v message_number: STRING; v message_text: STRING; v logfile_name: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v number_l: STRING; v message_text_u: STRING; v sapshcut_parameters: STRING;
177
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_System_Log Event slots R/3_System_Log attribute group v managed_system: STRING; v entry_time: STRING; v instance_name: STRING; v task_type: STRING; v client: STRING; v user: STRING; v transaction_code: STRING; v program_name: STRING; v development_class: STRING; v terminal: STRING; v message_number: STRING; v message_class: STRING; v message_class_enum: STRING; v message_text: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v record_number: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v message_text_u: STRING; v program_name_u: STRING; v sapshcut_parameters: STRING; v record_count: INTEGER; ITM_R3_System_Log_details R/3_System_Log_details attribute group v managed_system: STRING; v message_number: STRING; v message_class: STRING; v message_class_enum: STRING; v message_description: STRING; v message_text: STRING; v logon_parameters: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v record_number: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v entry_time: STRING; v message_description_u: STRING; v message_text_u: STRING; v sapshcut_parameters: STRING;
178
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Spool_Requests Event slots R/3_Spool_Requests attribute group v managed_system: STRING; v spool_number: INTEGER; v spool_title: STRING; v client: STRING; v creator: STRING; v create_time: STRING; v output_device: STRING; v output_format: STRING; v recipient: STRING; v department: STRING; v copies: INTEGER; v size: INTEGER; v authorization: STRING; v delete_time: STRING; v cover_page: STRING; v cover_page_enum: STRING; v delete_after_print: STRING; v delete_after_print_enum: STRING; v request_closed: STRING; v request_closed_enum: STRING; v total_print_requests: INTEGER; v processed_print_requests: INTEGER; v error_print_requests: INTEGER; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v output_device_u: STRING; v output_format_u: STRING; v department_u: STRING; v sapshcut_parameters: STRING;
179
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Output_Requests Event slots R/3_Output_Requests attribute group v managed_system: STRING; v spool_number: INTEGER; v spool_title: STRING; v client: STRING; v creator: STRING; v print_request_time: STRING; v print_pending_time: INTEGER; v print_pending_time_enum: STRING; v output_device: STRING; v output_format: STRING; v recipient: STRING; v department: STRING; v copies: INTEGER; v size: INTEGER; v processed_print_requests: INTEGER; v error_print_requests: INTEGER; v failed_print_requests: INTEGER; v print_status: STRING; v print_status_enum: STRING; v print_reason: STRING; v print_reason_enum: STRING; v host_spool_id: STRING; v spooler_host_name: STRING; v spooler_system_name: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v spool_title_u: STRING; v output_device_u: STRING; v output_format_u: STRING; v department_u: STRING; v sapshcut_parameters: STRING;
180
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_File_Systems Event slots R/3_File_Systems attribute group v managed_system: STRING; v name: STRING; v capacity: INTEGER; v size_free: INTEGER; v size_used: INTEGER; v size_used_percent: INTEGER; v message: STRING; v full_forecast: INTEGER; v full_forecast_enum: STRING; v relative_hour: STRING; v sample_time: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v name_u: STRING; v message_u: STRING; v sapshcut_parameters: STRING;
181
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Buffer_Performance Event slots R/3_Buffer_Performance attribute group v managed_system: STRING; v name: STRING; v hitratio: REAL; v requests: INTEGER; v requests_enum: STRING; v hits: INTEGER; v hits_enum: STRING; v misses: INTEGER; v misses_enum: STRING; v db_access_quality: REAL; v db_accesses: INTEGER; v db_accesses_enum: STRING; v db_accesses_saved: INTEGER; v db_accesses_saved_enum: STRING; v size_allocated: INTEGER; v size_allocated_enum: STRING; v size_used: INTEGER; v size_used_enum: STRING; v size_free: INTEGER; v size_free_enum: STRING; v directory_allocated: INTEGER; v directory_allocated_enum: STRING; v directory_used: INTEGER; v directory_used_enum: STRING; v directory_free: INTEGER; v directory_free_enum: STRING; v objects_swapped: INTEGER; v objects_swapped_enum: STRING; v frames_swapped: INTEGER; v frames_swapped_enum: STRING; v total_resets: INTEGER; v total_resets_enum: STRING; v last_reset: STRING; v objects_in_buffer: INTEGER; v objects_in_buffer_enum: STRING; v inserts: INTEGER; v inserts_enum: STRING; v changes: INTEGER; v changes_enum: STRING; v deletes: INTEGER; v deletes_enum: STRING; v sample_time: STRING; v logon_parameters: STRING;
182
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Buffer_Performance (continued) Event slots R/3_Buffer_Performance attribute group v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v size_free_percent: INTEGER; v size_free_percent_enum: STRING; v size_used_percent: INTEGER; v size_used_percent_enum: STRING; v size_in_memory: INTEGER; v size_in_memory_enum: STRING; v size_on_disk: INTEGER; v size_on_disk_enum: STRING; v max_used: INTEGER; v max_used_enum: STRING; v max_used_percent: INTEGER; v max_used_percent_enum: STRING; v directory_used_percent: INTEGER; v directory_used_percent_enum: STRING; v directory_free_percent: INTEGER; v directory_free_percent_enum: STRING; v sapshcut_parameters: STRING; v size_reserved: INTEGER; v size_reserved_percent: INTEGER; v encoded_name: STRING; v encoded_name_enum: STRING;
183
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Batch_Data_Create Event slots R/3_Batch_Data_Create attribute group v managed_system: STRING; v session_name: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v created: STRING; v locked_until: STRING; v creator: STRING; v authorization: STRING; v client: STRING; v last_changed: STRING; v start_mode: STRING; v start_mode_enum: STRING; v total_transactions: INTEGER; v total_screens: INTEGER; v error_transactions: INTEGER; v error_screens: INTEGER; v pending_transactions: INTEGER; v pending_screens: INTEGER; v completed_transactions: INTEGER; v completed_screens: INTEGER; v deleted_transactions: INTEGER; v deleted_screens: INTEGER; v queue_id: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v session_name_u: STRING; v sapshcut_parameters: STRING;
184
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Batch_Data_Create_Log Event slots R/3_Batch_Data_Create_Log attribute group v managed_system: STRING; v session_name: STRING; v created: STRING; v message_time: STRING; v transaction: STRING; v screen_number: STRING; v message_number: STRING; v message_text: STRING; v queue_id: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v execution_host: STRING; v session_name_u: STRING; v transaction_u: STRING; v message_text_u: STRING; v sapshcut_parameters: STRING;
185
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Data_Base_Summary Event slots R/3_Data_Base_Summary attribute group v managed_system: STRING; v name: STRING; v database: STRING; v object_type: STRING; v total_number: INTEGER; v total_size: INTEGER; v total_used: INTEGER; v total_used_enum: STRING; v total_used_percent: INTEGER; v total_used_percent_enum: STRING; v total_free: INTEGER; v total_free_enum: STRING; v total_free_percent: INTEGER; v total_free_percent_enum: STRING; v minimum_free: INTEGER; v minimum_free_enum: STRING; v freespace_problems: INTEGER; v freespace_problems_enum: STRING; v missing_in_database: INTEGER; v missing_in_database_enum: STRING; v missing_in_ddic: INTEGER; v missing_in_ddic_enum: STRING; v analysis_time: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v sapshcut_parameters: STRING;
186
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Data_Base_Detail Event slots R/3_Data_Base_Detail attribute group v managed_system: STRING; v object_name: STRING; v object_type: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v space_critical: STRING; v space_critical_enum: STRING; v size: INTEGER; v size_change_per_day: INTEGER; v size_used: INTEGER; v size_used_enum: STRING; v size_used_percent: INTEGER; v size_used_percent_enum: STRING; v used_change_per_day: INTEGER; v used_change_per_day_enum: STRING; v size_free: INTEGER; v size_free_enum: STRING; v size_free_percent: INTEGER; v size_free_percent_enum: STRING; v minimum_free: INTEGER; v minimum_free_enum: STRING; v maximum_free: INTEGER; v maximum_free_enum: STRING; v extents: INTEGER; v extents_change_per_day: INTEGER; v max__next_extent: INTEGER; v max__next_extent_enum: STRING; v tables__and__indices: INTEGER; v tables__and__indices_enum: STRING; v tables__and__indices_change_per_day: INTEGER; v tables__and__indices_change_per_day_enum: STRING; v files: INTEGER; v files_enum: STRING; v analysis_time: STRING; v logon_parameters: STRING; v system_name: STRING; v system_name_enum: STRING; v sapshcut_parameters: STRING;
187
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Set_Default_Sample_Period Event slots R/3_Set_Default_Sample_Period attribute group v managed_system: STRING; v message: STRING; v rfc_function: STRING; v default_period: STRING; v system_name: STRING; v system_name_enum: STRING; v sapshcut_parameters: STRING; ITM_R3_Perform_Requested_Action R/3_Perform_Requested_Action attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v action: STRING; v message: STRING; v message_u: STRING; v sapshcut_parameters: STRING; v return_code: INTEGER; v return_value: STRING; ITM_R3_Active_Users R/3_Active_Users attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v client: STRING; v userid: STRING; v terminal: STRING; v ip_address: STRING; v transaction_code: STRING; v time: STRING; v external_sessions: INTEGER; v internal_sessions: INTEGER; v echoed_to_session: STRING; v session_number: INTEGER; v session_title: STRING; v session_time: STRING; v user_key: INTEGER; v user_roll_size: INTEGER; v user_page_size: INTEGER; v user_total_memory: INTEGER; v user_private_memory: INTEGER; v sample_time: STRING; v logon_parameters: STRING; v session_title_u: STRING; v sapshcut_parameters: STRING;
188
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_User_Information Event slots R/3_User_Information attribute group v system_name: STRING; v system_name_enum: STRING; v userid: STRING; v client: STRING; v full_name: STRING; v telephone_number: STRING; v fax_number: STRING; v function: STRING; v department: STRING; v cost_center: STRING; v country: STRING; v building: STRING; v room: STRING; v logon_parameters: STRING; v description: STRING; v ksa_value: STRING; v full_name_u: STRING; v function_u: STRING; v department_u: STRING; v cost_center_u: STRING; v country_u: STRING; v building_u: STRING; v room_u: STRING; v sapshcut_parameters: STRING;
189
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Work_Processes Event slots R/3_Work_Processes attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v number: INTEGER; v type: STRING; v type_enum: STRING; v os_process_id: INTEGER; v ksa_status: STRING; v ksa_status_enum: STRING; v status_reason: STRING; v status_reason_enum: STRING; v restart_after_error: STRING; v restart_after_error_enum: STRING; v errors: INTEGER; v cpu_time: INTEGER; v elapsed_time: INTEGER; v elapsed_time_enum: STRING; v client: STRING; v userid: STRING; v userid_enum: STRING; v transaction_code: STRING; v program: STRING; v filler: STRING; v action: STRING; v action_enum: STRING; v table_name: STRING; v wait_information: STRING; v wait_start_time: STRING; v database_reads: INTEGER; v database_reads_time: INTEGER; v database_changes: INTEGER; v database_changes_time: INTEGER; v roll_in-out_count: INTEGER; v roll_in-out_time: INTEGER; v process_roll_size: INTEGER; v process_page_size: INTEGER; v process_total_memory: INTEGER; v process_private_memory: INTEGER; v sample_time: STRING; v logon_parameters: STRING; v transaction_code_u: STRING; v program_u: STRING; v wait_information_u: STRING; v sapshcut_parameters: STRING;
190
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_ABAP_Dumps Event slots R/3_ABAP_Dumps attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v dump_title: STRING; v program_name: STRING; v include_name: STRING; v line_number: INTEGER; v line_number_enum: STRING; v create_time: STRING; v userid: STRING; v client: STRING; v host: STRING; v hold_status: STRING; v hold_status_enum: STRING; v mode_number: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v program_name_u: STRING; v include_name_u: STRING; v sapshcut_parameters: STRING; ITM_R3_Lock_Entries R/3_Lock_Entries attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v client: STRING; v userid: STRING; v host: STRING; v system_number: STRING; v work_process: INTEGER; v create_time: STRING; v lock_age: INTEGER; v transaction_code: STRING; v lock_object_name: STRING; v group: STRING; v argument: STRING; v owner: STRING; v update_owner: STRING; v hold_count: INTEGER; v update_hold_count: INTEGER; v backup_flag: STRING; v sample_time: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING;
191
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Updates_Information Event slots R/3_Updates_Information attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v client: STRING; v userid: STRING; v time: STRING; v transaction_code: STRING; v program: STRING; v function_module: STRING; v state_code: STRING; v state_code_enum: STRING; v state_description: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v status_number: INTEGER; v status_description: STRING; v error: STRING; v update_key: STRING; v update_server: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v state_description_u: STRING; v status_description_u: STRING; v error_u: STRING; v program_u: STRING; v sapshcut_parameters: STRING;
192
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Gateway_Connections Event slots R/3_Gateway_Connections attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v connection_number: INTEGER; v in_use: STRING; v in_use_enum: STRING; v local_logical_unit_name: STRING; v local_transaction_program_name: STRING; v local_appc_version: INTEGER; v remote_logical_unit_name: STRING; v remote_transaction_program_name: STRING; v remote_appc_version: INTEGER; v userid: STRING; v ksa_status: STRING; v symbolic_destination_name: STRING; v conversation_identifier: STRING; v trace_level: INTEGER; v cpic_return_code: INTEGER; v sap_return_code: INTEGER; v request_time: STRING; v local_host: STRING; v local_ip_address: STRING; v remote_host: STRING; v remote_ip_address: STRING; v system_type: STRING; v registration_status: STRING; v connection_speed: STRING; v number_of_connections: INTEGER; v sample_time: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING;
193
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Gateway_Statistics Event slots R/3_Gateway_Statistics attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v statistics_active: STRING; v statistics_active_enum: STRING; v connect_accepts: INTEGER; v connect_accepts_enum: STRING; v cminits: INTEGER; v cminits_enum: STRING; v timeouts: INTEGER; v timeouts_enum: STRING; v overflows: INTEGER; v overflows_enum: STRING; v current_overflow_usage: REAL; v current_overflow_usage_enum: STRING; v max_overflow_usage: REAL; v max_overflow_usage_enum: STRING; v current_data_stack: INTEGER; v current_data_stack_enum: STRING; v max_data_stack: INTEGER; v max_data_stack_enum: STRING; v data_stack_limit: INTEGER; v data_stack_limit_enum: STRING; v connection_with_maximum_stack: INTEGER; v connection_with_maximum_stack_enum: STRING; v reader_requests: INTEGER; v reader_requests_enum: STRING; v total_reader_time: REAL; v total_reader_time_enum: STRING; v min_reader_time: REAL; v min_reader_time_enum: STRING; v max_reader_time: REAL; v max_reader_time_enum: STRING; v avg_reader_time: REAL; v avg_reader_time_enum: STRING; v longest_reader_request: STRING; v work_process_requests: INTEGER; v work_process_requests_enum: STRING;
194
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Gateway_Statistics (continued) Event slots v total_work_process_time: REAL; v total_work_process_time_enum: STRING; v min__work_process_time: REAL; v min__work_process_time_enum: STRING; v max__work_process_time: REAL; v max__work_process_time_enum: STRING; v avg__work_process_time: REAL; v avg__work_process_time_enum: STRING; v tcp_reads: INTEGER; v tcp_reads_enum: STRING; v fragmented_tcp_reads: INTEGER; v fragmented_tcp_reads_enum: STRING; v tcp_read_size: INTEGER; v tcp_read_size_enum: STRING; v total_tcp_read_time: REAL; v total_tcp_read_time_enum: STRING; v min_tcp_read_time: REAL; v min_tcp_read_time_enum: STRING; v max_tcp_read_time: REAL; v max_tcp_read_time_enum: STRING; v avg_tcp_read_time: REAL; v avg_tcp_read_time_enum: STRING; v tcp_writes: INTEGER; v tcp_writes_enum: STRING; v fragmented_tcp_writes: INTEGER; v fragmented_tcp_writes_enum: STRING; v tcp_write_size: INTEGER; v tcp_write_size_enum: STRING; v total_tcp_write_time: REAL; v total_tcp_write_time_enum: STRING; v min_tcp_write_time: REAL; v min_tcp_write_time_enum: STRING; v max_tcp_write_time: REAL; v max_tcp_write_time_enum: STRING; v avg_tcp_write_time: REAL; v avg_tcp_write_time_enum: STRING; v tcp_read_rate: INTEGER; v tcp_read_rate_enum: STRING; v tcp_write_rate: INTEGER; v tcp_write_rate_enum: STRING; v tcp_errors: INTEGER; v tcp_errors_enum: STRING;
195
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Gateway_Statistics (continued) Event slots v cpic_reads: INTEGER; v cpic_reads_enum: STRING; v cpic_read_size: INTEGER; v cpic_read_size_enum: STRING; v total_cpic_read_time: REAL; v total_cpic_read_time_enum: STRING; v min_cpic_read_time: REAL; v min_cpic_read_time_enum: STRING; v max_cpic_read_time: REAL; v max_cpic_read_time_enum: STRING; v avg_cpic_read_time: REAL; v avg_cpic_read_time_enum: STRING; v cpic_writes: INTEGER; v cpic_writes_enum: STRING; v cpic_write_size: INTEGER; v cpic_write_size_enum: STRING; v total_cpic_write_time: REAL; v total_cpic_write_time_enum: STRING; v min_cpic_write_time: REAL; v min_cpic_write_time_enum: STRING; v max_cpic_write_time: REAL; v max_cpic_write_time_enum: STRING; v avg_cpic_write_time: REAL; v avg_cpic_write_time_enum: STRING; v cpic_read_rate: INTEGER; v cpic_read_rate_enum: STRING; v cpic_write_rate: INTEGER; v cpic_write_rate_enum: STRING; v cpic_errors: INTEGER; v cpic_errors_enum: STRING; v sample_time: STRING; v logon_parameters: STRING; v description: STRING; v ksa_value: STRING; v sapshcut_parameters: STRING;
196
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Number_Range_Buffer_Summary Event slots R/3_Number_Range_Buffer_Summary attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v maximum_entries: INTEGER; v current_entries: INTEGER; v maximum_indexes: INTEGER; v current_indexes: INTEGER; v buffer_size: INTEGER; v buffer_calls: INTEGER; v get_calls: INTEGER; v server_calls: INTEGER; v database_calls: INTEGER; v conflicts: INTEGER; v timeouts: INTEGER; v buffer_responses_less_than_50us: INTEGER; v buffer_responses_less_than_1ms: INTEGER; v buffer_responses_1ms_or_greater: INTEGER; v server_responses_less_than_1ms: INTEGER; v server_responses_less_than_50ms: INTEGER; v server_responses_50ms_or_greater: INTEGER; v sample_time: STRING; v logon_parameters: STRING; v description: STRING; v ksa_value: STRING; v sapshcut_parameters: STRING;
197
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Number_Range_Buffer_Details Event slots R/3_Number_Range_Buffer_Details attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v client: STRING; v object_name: STRING; v sub-object_name: STRING; v range_number: STRING; v year: INTEGER; v year_enum: STRING; v from_number: STRING; v to_number: STRING; v last_number: STRING; v external_range: STRING; v external_range_enum: STRING; v interval_to_number: STRING; v sample_time: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING; ITM_R3_Developer_Traces R/3_Developer_Traces attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v file_name: STRING; v system_component: STRING; v log_data: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING; ITM_R3_Saprouter_Log R/3_Saprouter_Log attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v file_name: STRING; v date_time: STRING; v log_data: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING;
198
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Database_Logs Event slots R/3_Database_Logs attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v file_name: STRING; v log_data: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING; ITM_R3_Transactional_RFC R/3_Transactional_RFC attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v send_receive: STRING; v send_receive_enum: STRING; v userid: STRING; v function_module: STRING; v target_name: STRING; v time: STRING; v ksa_status: STRING; v transaction_id: STRING; v ksa_hostname: STRING; v transaction_code: STRING; v client: STRING; v program: STRING; v data_size: REAL; v retries: INTEGER; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v function_module_u: STRING; v target_name_u: STRING; v status_u: STRING; v transaction_code_u: STRING; v program_u: STRING; v sapshcut_parameters: STRING;
199
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Logon_Groups Event slots R/3_Logon_Groups attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v name: STRING; v type: STRING; v type_enum: STRING; v instance_name: STRING; v maximum_response_time: INTEGER; v maximum_response_time_enum: STRING; v current_response_time: INTEGER; v current_response_time_enum: STRING; v event_frequency: INTEGER; v event_frequency_enum: STRING; v maximum_users: INTEGER; v maximum_users_enum: STRING; v current_users: INTEGER; v current_users_enum: STRING; v alternate_ip_address: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v statistics_sample_time: STRING; v current_favorite: STRING; v current_favorite_enum: STRING; v sample_time: STRING; v logon_parameters: STRING; v name_u: STRING; v sapshcut_parameters: STRING;
200
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Intermediate_Documents Event slots R/3_Intermediate_Documents attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v number: INTEGER; v type: STRING; v create_time: STRING; v update_time: STRING; v direction: STRING; v direction_enum: STRING; v message_type: STRING; v message_code: STRING; v message_function: STRING; v test_production: STRING; v test_production_enum: STRING; v partner_port: STRING; v partner_type: STRING; v partner_function: STRING; v partner_name: STRING; v status_number: STRING; v status_description: STRING; v status_information: STRING; v status_for_statistics: STRING; v status_for_statistics_enum: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v type_u: STRING; v status_description_u: STRING; v status_information_u: STRING; v sapshcut_parameters: STRING; ITM_R3_EDI_Files R/3_EDI_Files attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v file_name: STRING; v last_record: INTEGER; v last_idoc: INTEGER; v delete_file: STRING; v delete_file_enum: STRING; v sample_time: STRING; v logon_parameters: STRING; v file_name_u: STRING; v sapshcut_parameters: STRING;
201
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Logon_Information Event slots R/3_Logon_Information attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v instance_name: STRING; v client: STRING; v userid: STRING; v userid_enum: STRING; v userid_type: STRING; v userid_type_enum: STRING; v userid_state: STRING; v userid_state_enum: STRING; v terminal: STRING; v ip_address: STRING; v logon_logoff: STRING; v logon_logoff_enum: STRING; v time: STRING; v session_duration: INTEGER; v session_duration_enum: STRING; v invalid_password_count: INTEGER; v invalid_password_count_enum: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v sapshcut_parameters: STRING;
202
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_Archive_Monitor Event slots R/3_Archive_Monitor attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v open_spool_requests: INTEGER; v open_spool_requests_enum: STRING; v open_spool_errors: INTEGER; v open_spool_errors_enum: STRING; v transactional_rfc_requests: INTEGER; v transactional_rfc_requests_enum: STRING; v open_asynchronous_requests: INTEGER; v open_asynchronous_errors: INTEGER; v archiving_queues: INTEGER; v archiving_queues_enum: STRING; v archiving_errors: INTEGER; v archiving_errors_enum: STRING; v confirmation_queues: INTEGER; v confirmation_queues_enum: STRING; v confirmation_errors: INTEGER; v confirmation_errors_enum: STRING; v retrieval_queues: INTEGER; v retrieval_queues_enum: STRING; v retrieval_errors: INTEGER; v retrieval_errors_enum: STRING; v background_scheduled: INTEGER; v background_archiving: INTEGER; v background_confirmation: INTEGER; v background_retrieval: INTEGER; v background_file_processing: INTEGER; v background_file_processing_enum: STRING; v open_bar_codes: INTEGER; v bar_code_archive_files: INTEGER; v logging_entries: INTEGER; v archive_device_status: STRING; v archive_device_status_enum: STRING; v sample_time: STRING; v logon_parameters: STRING; v description: STRING; v ksa_value: STRING; v sapshcut_parameters: STRING;
203
Table 10. Overview of event slots to event classes (continued) IBM Tivoli Enterprise Console event class ITM_R3_SAP_Office_Inbox Event slots R/3_SAP_Office_Inbox attribute group v managed_system: STRING; v system_name: STRING; v system_name_enum: STRING; v userid: STRING; v client: STRING; v user_name: STRING; v mail_type: STRING; v mail_name: STRING; v mail_title: STRING; v ksa_status: STRING; v ksa_status_enum: STRING; v sent_time: STRING; v received_time: STRING; v open_time: STRING; v expiration_time: STRING; v inbox_pending_time: INTEGER; v inbox_pending_time_enum: STRING; v author: STRING; v owner: STRING; v attachments: INTEGER; v action_type: STRING; v action_name: STRING; v size: INTEGER; v priority: INTEGER; v sensitivity: STRING; v sensitivity_enum: STRING; v express: STRING; v express_enum: STRING; v changeable: STRING; v changeable_enum: STRING; v attachment_type: STRING; v sample_interval_start: STRING; v sample_interval_end: STRING; v logon_parameters: STRING; v mail_type_u: STRING; v mail_name_u: STRING; v mail_title_u: STRING; v action_type_u: STRING; v action_name_u: STRING; v sapshcut_parameters: STRING;
204
Appendix B. Commands for utilities

IBM Tivoli Monitoring commands are run from the command line. This appendix describes the commands for the Monitoring Agent for mySAP utilities. Input strings to these utilities are provided by the Tivoli Enterprise Portal in UTF-8. For installation and configuration commands, see the IBM Tivoli Monitoring Installation and Setup Guide; for configuration and administrative commands, see the IBM Tivoli Monitoring Administrators Guide. For situation commands, see the IBM Tivoli Monitoring Users Guide. Note: If you are observing the same reporting in the portal user interface as you are at the command line, there may be some minor variance in the values. The following information is provided for each command: Description Purpose of the command. CLI syntax Syntax for the command that you enter on the command line. A list of the parameters for the command and a definition of each parameter follow the command name. CLI example The example for the command contains a brief description of the example and an example of the syntax. Return values Information that the command returns. Related commands Name and cross-reference to any other related commands.
205
ksanfy Description
Use the ksanfy command to run the ksar3nfy program. By using ksanfy, you can set or override environment variables needed by the ksar3nfy program. Note: The command is called ksanfy.bat on Windows and ksanfy on UNIX.
CLI syntax
ksanfy " [{A | ACTION}({D | DIALOG} | {F | FUNCTION} | {P | PROGRAM} | {R | REPORT} | {T | TRANSACTION})] [{C | CHANGEABLE}({Y | YES} | {N | NO})] [{E | EXPRESS}({Y | YES} | {N | NO})] [{M | MESSAGE}(message)] [{N | NAME}(mail_name)] [{O | OBJECT}(object_name)] [{P | PRIORITY}(priority)] [{R | RECIPIENT}(recipient_id)] [{S | SENSITIVITY}({F | FUNCTIONAL} | {P | PRIVATE} | {S | STANDARD})] [{T | TITLE}(mail_title)] [{U | USERTYPE}({O | OFFICE} | {P | PRIVATE} | {S | SHARED} {U | USERID})] "
Note: The command parameter syntax for ksanfy is the same as for ksar3nfy. Refer to the command syntax for ksar3nfy for a full description of the parameters.
CLI example
To send a mail item to a standard mySAP user PERFADMIN with the message "Transaction Performance Poor", attach the transaction ST03 to the mail as follows:
ksanfy "Recipient(PERFADMIN) Message(Transaction Performance Poor) Object(ST03)"
Return values
The ksanfy program returns the RFC return code from the ksar3nfy program.
Related commands
See ksar3nfy on page 207.
206
ksar3nfy Description
Use the ksar3nfy command to send SAP Office email to mySAP users. Note: The command is called ksar3nfy.exe on Windows and ksar3nfy on UNIX.
CLI syntax
ksar3nfy "[{A | ACTION}({D | DIALOG} | {F | FUNCTION} | {P | PROGRAM} | {R | REPORT} | {T | TRANSACTION})] [{C | CHANGEABLE}({Y | YES} | {N | NO})] [{E | EXPRESS}({Y | YES} | {N | NO})] [{M | MESSAGE}(message)] [{N | NAME}(mail_name)] [{O | OBJECT}(object_name)] [{P | PRIORITY}(priority)] [{R | RECIPIENT}(recipient_id)] [{S | SENSITIVITY}({F | FUNCTIONAL} | {P | PRIVATE} | {S | STANDARD})] [{T | TITLE}(mail_title)] [{U | USERTYPE}({O | OFFICE} | {P | PRIVATE} | {S | SHARED} {U | USERID})] "
Notes: 1. All keywords are case insensitive. All keywords can be abbreviated to any number of characters. 2. The parameter string must be enclosed in double quotes. 3. Parameters can be separated with spaces or commas, or have no separation at all. 4. All recognized keywords and values are validated within mySAP. All unrecognized and irrelevant keywords are ignored. Where: A | ACTION Attach an executable action of one of the following types to the mail item: v v v v v DIALOG Dialog module FUNCTION Function module PROGRAM Program REPORT Report TRANSACTION Transaction
If ACTION is specified, OBJECT must also be specified. If OBJECT is specified, the default ACTION is TRANSACTION. If OBJECT is not specified, the default ACTION is no action. C | CHANGEABLE Specify YES to allow the recipients to change the mail prior to forwarding it. Specify NO to prevent the recipient from changing the mail. The default is YES. E | EXPRESS Specify YES to use SAPOffice express mail. Specify NO to use standard SAPOffice mail. The default is NO.
207
M | MESSAGE Send the message message in the body of the mail item. message can be a simple string up to 255 characters in length or the name of a file containing the mail message. Each line of the file can contain up to 255 characters. The default is "Mail from IBMMON". N | NAME Use the name, mail_name, for the mail item. mail_name can be 12 characters in length. The default is "IBMMON MAIL". O | OBJECT The name of the executable object is object_name. object_name is the name of a dialog module, the name of a function module, the name of a report (program), or the name of a transaction. The default is no action name. P | PRIORITY Send the mail with a priority of priority. priority can be any number from 0 through 9. The default is 9. R | RECIPIENT Send the mail to recipients recipient_id. recipient_id can specify one of the following: v Standard SAP user ID v SAPOffice user v SAPOffice shared distribution list v SAPOffice private distribution list v Name of a file containing a list of any of the previous four recipients If a file is specified, each line of the file is a separate recipient definition. The first word of each line can define a standard SAP user ID, SAPOffice user, or SAPOffice private distribution list. The second optional word defines the type of recipient. The third optional word specifies whether to use SAPOffice Express mail. (See the descriptions for USERTYPE and EXPRESS for possible values for the second and third words). The default recipient is the standard SAP user ID that ksar3nfy used to log on to the mySAP system. S | SENSITIVITY Specify the sensitivity of the mail. Sensitivity can be FUNCTIONAL, PRIVATE, or STANDARD. The default is STANDARD T | TITLE Use the title mail_title for the mail item. mail_title can be up to 50 characters in length. The default is the first line of the mail message if message is specified, or "Mail from IBMMON" if no message is specified. U | USERTYPE Specify the USERTYPE as one of the following: v OFFICE - for a SAPOffice user v PRIVATE - for a SAPOffice private distribution list v SHARED - for a SAPOffice shared distribution list v USERID - for a standard mySAP user ID The default is USERID.
CLI example
To send a mail item to a standard mySAP user PERFADMIN with the message "Transaction Performance Poor", attach the transaction ST03 to the mail as follows:
208
ksar3nfy Recipient(PERFADMIN) Message(Transaction Performance Poor) Object(ST03)
or
ksar3nfy R(DISTLIST) M(mail.txt) E(Y) C(Y)
To send an express mail item to an SAPOffice shared distribution list of DISTLIST, the mail message is in file MAIL.TXT, and the mail is changeable by the recipients:
ksar3nfy Recipient(DISTLIST) Message(mail.txt) Express(Yes) Changeable(Yes)
or
ksar3nfy R(DISTLIST) M(mail.txt) E(Y) C(Y)
Return values
The ksar3nfy program returns the RFC return code.
Related commands
See ksanfy on page 206.
209
ksar3 Description
Use the ksar3 command to run the ksar3exe program. By using ksar3, you can set or override environment variables needed by the ksar3exe program. Note: The command is called ksar3.bat on Windows and ksar3 on UNIX.
CLI syntax
ksar3 " [{A | ABAP}(abap_name)] [{C | CHANGE}(name=value,...)] [{D | DESTINATION}(destination_name)] [{E | EXPORT}(name=value,...)] [{F | FUNCTION}(function_module_name)] [{I | IMPORT}(name=value,...)] [{J | JOB}(job_name, job_number)] [{R | REPORT}(file_name)] [{S | SAPGUI}({Y | YES} | {N | NO})] [{T | TRANSACTION}(transaction_name)] [{V | VARIANT}(variant_name | name-op-value,...)] [{W | WAIT}({Y | YES} | {N | NO})] [{Z | ZTABLES}(name=value,...)] " Note: The command parameter syntax for ksar3 is the same as for ksar3exe. Refer to the command syntax for ksar3exe for a full description of the parameters
CLI example
The following command runs an ABAP named MYABAP:
ksar3 "ABAP(MYABAP)"
Return values
The ksar3 program returns the RFC return code from the ksar3exe program
Related commands
See ksar3exe on page 211.
210
ksar3exe Description
Use the ksar3exe command to run a function inside a mySAP system. Note: The command is called ksar3exe.exe on Windows and ksar3exe on UNIX.
CLI syntax
ksar3exe " [{A | ABAP}(abap_name)] [{C | CHANGE}(name=value,...)] [{D | DESTINATION}(destination_name)] [{E | EXPORT}(name=value,...)] [{F | FUNCTION}(function_module_name)] [{I | IMPORT}(name=value,...)] [{J | JOB}(job_name, job_number)] [{R | REPORT}(file_name)] [{S | SAPGUI}({Y | YES} | {N | NO})] [{T | TRANSACTION}(transaction_name)] [{V | VARIANT}(variant_name | name-op-value,...)] [{W | WAIT}({Y | YES} | {N | NO})] [{Z | ZTABLES}(name=value,...)]" Notes: 1. All keywords are case insensitive. All keywords can be abbreviated to any number of characters. 2. The parameter string must be enclosed in double quotes. 3. Parameters can be separated with spaces or commas, or have no separation at all. 4. All recognized keywords and values are validated within mySAP. All unrecognized and irrelevant keywords are ignored. Where: A | ABAP Run ABAP named abap_name. There is no default. C | CHANGE Same as EXPORT, except these parameters are used by the function module and modified values are returned by the function module. As with EXPORT, the type of variable is automatically set by ksar3exe. If WAIT(YES) and REPORT(file_name) are specified, the original and modified values returned by the function module are printed in file_name. D | DESTINATION If the requested Job or Function must run on a specific instance, run it on instance destination_name. There is no default. E | EXPORT If the requested action is a function module that requires import parameters, export the parameters by specifying them here. name value Parameter name expected by the function module Value for the parameter
Separate multiple name and value combinations with a comma.
211
The type of the parameter (character, integer, hex, and so on) is automatically handled by ksar3exe. For example, function module MYTEST expects to import a character parameter named CHARS and an integer parameter named NUMBER. Specify EXPORT(CHARS=charvalue,NUMBER=nu mvalue). charvalue is automatically typed to character. numvalue is automatically typed to integer. F | FUNCTION Run function module function_module_name. There is no default I | IMPORT Same as EXPORT, except these parameters are returned by the function module. As with EXPORT, the type of variable is automatically set by ksar3exe. If WAIT(YES) and REPORT(file_name) are specified, the values returned by the function module are printed in file_name. J | JOB Run a job named job_name. Optionally, the job_number job number can be specified if multiple different jobs with the same name exist. The specified job must be in SCHEDULED or RELEASED status in mySAP. ksar3exe makes a copy of the job and runs it immediately. The original job is left unchanged and can be used again. There is no default. R | REPORT If the report output from the requested action is required in a file, specify the file_name. Use STDOUT if the report must be sent to standard out. If the requested action was a job, the job log and all spooled output is written to file_name. Defaults to STDOUT unless a transaction is requested, in which case there is no default. S | SAPGUI If the requested action displays an SAPGUI, specify YES (or Y). If no screen is to be displayed, specify NO (or N). Defaults is NO unless a transaction is requested, in which case the default is YES. T | TRANSACTION Run transaction transaction_name. The Tivoli Enterprise Portal passes this parameter to ksar3exe when you request a particular mySAP transaction from the Tivoli Enterprise Portal. There is no default. V | VARIANT If the requested ABAP requires a variant and an appropriate variant is already defined in the mySAP system, use variant_name. There is no default If the requested ABAP requires a variant and an appropriate variant is not defined in the mySAP system, the parameters required by the ABAP can be specified individually as follows: name value op PARAMETER or SELECT-OPTIONS name expected by the ABAP Value for the PARAMETER or SELECT-OPTIONS Operator connecting the name and the value. Any of the following operators are accepted: v ^= Not equal v <> Not equal v <= Less than or equal v =< Less than or equal v ^> Less than or equal, not greater than
212
v v v v v v v
< Less than >= Greater than or equal => Greater than or equal ^< Greater than or equal, not less than > Greater than ~ Contains pattern ^~ Does not contain pattern
Separate multiple combinations of name-op-value with a comma. The type of the PARAMETER or SELECT-OPTIONS (character, integer, hex, and so on) is automatically handled by ksar3exe. To specify ranges for SELECT-OPTIONS, specify the lower limit, followed by the upper limit. For example, to specify a range of 1 through 9 to an ABAP that contains a SELECT-OPTIONS named NUMBERS, specify the variant as follows:
variant(numbers>=1,numbers<=9)
W | WAIT Specify YES (or Y) if ksar3exe must wait for the requested action to complete, specify NO (or N) if ksar3exe must not wait. Defaults to YES unless a transaction is requested, in which case, the default is NO. Z | ZTABLES Same as EXPORT, except these tables are returned by the function module. If WAIT(YES) and REPORT(file_name) are specified, the table row values returned by the function module are printed in file_name.
CLI example
The following command runs an ABAP named MYABAP:
ksar3exe "ABAP(MYABAP)"
The following command runs an ABAP named MYABAP with a variant name PRODRUN that is already saved in the mySAP system:
ksar3exe "A(MYABAP) VARIANT(PRODRUN)"
The following command runs the ST02 transaction:

ksar3exe "Transaction(ST02)"
Return values
The ksar3exe program returns the RFC return code.
Related commands
See ksar3 on page 210.
213
ksapwd Description
Use the ksapwd command to run the ksar3pwd program. By using ksapwd, you can set or override environment variables needed by the ksar3pwd program. Note: The command is called ksapwd.bat on Windows and ksapwd on UNIX.
CLI syntax
ksapwd" [{O | OUTPUT}(filename | STDOUT)] {P | PASSWORD}(password) " Note: The command parameter syntax for ksapwd is the same as for ksar3pwd. Refer to the command syntax for ksar3pwd for a full description of the parameters.
CLI example
To cause the password "tivoli" to be encrypted and written to the default file named ksa.pwd in the current directory, enter the following:
ksapwd PASSWORD(tivoli)
Return values
The ksapwd program returns the following values: 0 success 16 error
Related commands
See ksar3pwd on page 215.
214
ksar3pwd Description
Use the ksar3pwd command to encrypt a password for use with a mySAP user ID. Note: The command is called ksar3pwd.exe on Windows and ksar3pwd on UNIX.
CLI syntax
ksar3pwd [{O | OUTPUT}(filename | STDOUT)] {P | PASSWORD}(password) Notes: 1. All keywords except STDOUT are case insensitive. All keywords except STDOUT can be abbreviated to any number of characters. 2. The parameter string must be enclosed in double quotes. 3. Parameters can be separated with spaces, commas, or have no separation at all. Where: O | OUTPUT Enter as filename the name of the file into which the encrypted password is written. Enter a simple file name to have the file created in the current directory. Enter a full path and file name to have the file created in a directory other than the current directory. Enter STDOUT to have the encrypted password written to standard output instead of being written to a file. The default value is a file name of ksa.pwd in the current directory. P | PASSWORD Enter as password the password string to be encrypted.
CLI example
To cause the password "tivoli" to be encrypted and written to the default file named ksa.pwd in the current directory, enter:
ksar3pwd "PASSWORD(tivoli)"
To cause the password "other" to be encrypted and written to a file named pwd.txt in the /home directory, enter:
ksar3pwd "P(other) O (/home/pwd.txt)"
To cause the password "newpw" to be encrypted and displayed on your computer screen, enter:
ksar3pwd "PASSWORD(newpw) OUTPUT(STDOUT)"
Return values
The ksar3pwd program returns the following values: 0 success 16 error
Related commands
See ksapwd on page 214.
215
216

This appendix explains how to troubleshoot the IBM Tivoli Monitoring for Applications: mySAP Agent. Troubleshooting, or problem determination, is the process of determining why a product is malfunctioning. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Also, see Support information on page 241 for other problem-solving options.
Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing with this product, gather the information in Table 11 that relates to the problem.
Table 11. Information to gather before contacting IBM Software Support Information type Log files Description Collect trace log files from failing systems. Most logs are located in a logs subdirectory on the host computer. See Trace logging on page 218 for lists of all trace log files and their locations. See the IBM Tivoli Monitoring Users Guide for general information about the IBM Tivoli Monitoring environment. Release number and patch level Operating system version number and patch level Messages and other information displayed on the screen Version number for the following members of the monitoring environment: v IBM Tivoli Monitoring. Also provide the patch level, if available. v IBM Tivoli Monitoring for Applications: mySAP Agent Screen captures of incorrect output, if any. If the agent stops on UNIX systems, collect the core dump file from install_dir/bin directory, where install_dir is the directory path where you installed the monitoring agent.
mySAP information Operating system Messages Version numbers for IBM Tivoli Monitoring Screen captures (UNIX only) Core dump files
Version of the mySAP Use the /n/IBMMON/ITM_CONFIG transaction in the mySAP system to determine the agent transport installed installed and active transport number. After invoking the transaction, click About > IBM on a mySAP system Tivoli Monitoring for Applications: mySAP Agent, and look at the long text in the message, which looks similar to the following: Version: 6.1 Release: 00 Modification level: 00 Notification sequence: 00 Fixpack number: 0000 Date exported at IBM: 23.03.2006 Time exported at IBM: 03:43:32 Date imported into GS7: 27.03.2006 Time imported into GS7: 15:23:13 Current transport request: ITMK610_00064
Upload files for review to the following FTP site: ftp.emea.ibm.com. Log in as anonymous and place your files in the directory that corresponds to the IBM Tivoli Monitoring component that you use. See Contacting IBM Software Support on page 242 for more information about working with IBM Software Support.
217
Built-in problem determination features

The primary troubleshooting feature in the IBM Tivoli Monitoring for Applications: mySAP Agent is logging. Logging refers to the text messages and trace data generated by the IBM Tivoli Monitoring for Applications: mySAP Agent and is always enabled. Messages and trace data are sent to the files listed in Table 12 on page 220. Trace data captures transient information about the current operating environment when a component or application fails to operate as designed. IBM Software Support personnel use the captured trace information to determine the source of an error or unexpected condition. See Trace logging for more information.
Problem classification
The following types of problems might occur with the IBM Tivoli Monitoring for Applications: mySAP Agent: v Installation and Configuration v Agent v Tivoli Enterprise Portal v Workspaces v Situations v Take Action commands This appendix provides symptom descriptions and detailed workarounds for problems in these areas, as well as describing the logging capabilities of the monitoring agent. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
Trace logging
Trace logs capture information about the operating environment when component software fails to operate as intended. The principal log type is the RAS (Reliability, Availability, and Serviceability) trace log. These logs are in the English language only. The RAS trace log mechanism is available for all components of IBM Tivoli Monitoring. Most logs are located in a logs subdirectory on the host computer. See the following sections to learn how to configure and use trace logging: v Principal trace log files on page 220 v Examples: using trace logs on page 221 v Setting RAS trace parameters on page 222 v Enabling and disabling RFC tracing on page 225 Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as RAS1. IBM Software Support uses the information captured by trace logging to trace a problem to its source or to determine why an error occurred. The default configuration for trace logging, such as whether trace logging is enabled or disabled and trace level, depends on the source of the trace logging. Trace logging is always enabled.
218
Overview of log file management

Table 12 on page 220 provides the names, locations, and descriptions of RAS1 log files. The log file names adhere to the following naming convention:
hostname_product_instance_program_timestamp-nn.log
where: v hostname is the host name of the machine on which the monitoring component is running. v product is the two-character product code. For Monitoring Agent for mySAP, the product code is sa. v instance is the name of a 3-character identifier for the mySAP system that is being monitored. v program is the name of the program being run. v timestamp is an 8-character hexadecimal timestamp representing the time at which the program started. v nn is a rolling log suffix. See Examples of trace logging for details of log rolling.
Examples of trace logging

For example, if a mySAP system named PRD is being monitored from computer server01, the RAS log file for the Monitoring Agent for mySAP might be named as follows:
server01_sa_PRD_ksaagent_437fc59-01.log
For long-running programs, the nn suffix is used to maintain a short history of log files for that startup of the program. For example, the ksaagent program might have a series of log files as follows:
server01_sa_PRD_ksaagent_437fc59-01.log server01_sa_PRD_ksaagent_437fc59-02.log server01_sa_PRD_ksaagent_437fc59-03.log
As the program runs, the first log (nn=01) is preserved because it contains program startup information. The remaining logs roll." In other words, when the set of numbered logs reach a maximum size, the remaining logs are overwritten in sequence. Each time a program is started, a new timestamp is assigned to maintain a short program history. For example, if the Monitoring Agent for mySAP is started twice, it might have log files as follows:
server01_sa_PRD_ksaagent_437fc59-01.log server01_sa_PRD_ksaagent_437fc59-02.log server01_sa_PRD_ksaagent_437fc59-03.log server01_sa_PRD_ksaagent_537fc59-01.log server01_sa_PRD_ksaagent_537fc59-02.log server01_sa_PRD_ksaagent_537fc59-03.log
Each program that is started has its own log file. For example, the Monitoring Agent for mySAP has agent logs in this format:
server01_sa_PRD_ksaagent_437fc59-01.log
Note: When you communicate with IBM Software Support, you must capture and send the RAS1 log that matches any problem occurrence that you report.
219
Principal trace log files

Table 12 contains locations, file names, and descriptions of trace logs that can help determine the source of problems with agents.
Table 12. Trace log files for troubleshooting agents System where log is located On the computer that hosts the monitoring agent See Definitions of variables on page 221 for descriptions of the variables in the file names in column two. File name and path The RAS1 log files are named hostname_sa_instance_program_timestamp-nn.log and are located in the following path: v On Windows: install_dir\tmaitm6\logs v On UNIX: install_dir/logs Note: File names for RAS1 logs include a hexadecimal timestamp. Also on UNIX, a log with a decimal timestamp is provided: hostname_sa_timestamp.log and hostname_sa_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number. The *.LG0 log files are named instance_hostname_mySAP.LG0. These files are located in the following path: v On Windows: install_dir\tmaitm6\logs v On UNIX: install_dir/logs A new version of this file is generated every time the agent is restarted. IBM Tivoli Monitoring generates one backup copy of the *.LG0 file with the tag .LG1. View .LG0 to learn the following details regarding the current monitoring session: v Status of connectivity with the monitoring server. v Situations that were running. v The success or failure status of Take Action commands. Provides details about products that are installed. Note: Trace logging is enabled by default. A configuration step is not required to enable this tracing. Description Traces activity of the monitoring agent.
On the Tivoli Enterprise Monitoring Server See Definitions of variables on page 221 for descriptions of the variables in the file names in column two.
On UNIX: The candle_installation.log file in the install_dir/logs path. On Windows: The IBM Tivoli Monitoring timestamp.log file in the install_dir\InstallITM path. Unlike RAS1 log files, the name of the file displays a decimal timestamp. * The Warehouse_Configuration.log file is located in the following path on Windows: install_dir\InstallITM. The RAS1 log file is named hostname_ms_timestampnn.log and is located in the following path: v On Windows: install_dir\logs v On UNIX: install_dir/logs Note: File names for RAS1 logs include a hexadecimal timestamp Also on UNIX, a log with a decimal timestamp is provided: hostname_ms_timestamp.log and hostname_ms_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number.
Provides details about the configuration of data warehousing for historical reporting. Traces activity on the monitoring server.
220
Table 12. Trace log files for troubleshooting agents (continued) System where log is located On the Tivoli Enterprise Portal Server See Definitions of variables for descriptions of the variables in the file names in column two. File name and path The RAS1 log file is named hostname_cq_timestampnn.log and is located in the following path: v On Windows: install_dir\logs v On UNIX: install_dir/logs Note: File names for RAS1 logs include a hexadecimal timestamp Also on UNIX, a log with a decimal timestamp is provided: hostname_cq_timestamp.log and hostname_cq_timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID number. The TEPS_ODBC.log file is located in the following path on Windows: install_dir\InstallITM. When you enable historical reporting, this log file traces the status of the warehouse proxy agent. Description Traces activity on the portal server.
Definitions of variables for RAS1 logs: v hostname is the host name of the machine on which the agent is running. v install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can represent a path on the computer that hosts the monitoring server, the monitoring agent, or the portal server. v product is the two character product code. For Monitoring Agent for mySAP, the product code is sa. v instance refers to the 3-character identifier of the mySAP system that you are monitoring. v program is the name of the program being run. v timestamp is an eight-character hexadecimal timestamp representing the time at which the program started. v nn is a rolling log suffix. See Examples of trace logging on page 219 for details of log rolling.
See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the complete set of trace logs that are maintained on the monitoring server.
Examples: using trace logs

Typically IBM Software Support applies specialized knowledge to analyze trace logs to determine the source of problems. However, you can open trace logs in a text editor to learn some basic facts about your IBM Tivoli Monitoring environment. Example one This excerpt shows the typical .LG0 log for a failed connection between a monitoring agent and a monitoring server with the host name server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006, "location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE (Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK (Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>
Example two The following excerpts from the trace log for the monitoring server show the status of an agent, identified here as Remote node. The name of the computer where the agent is running is SERVER5B:
(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:KSA is ON-LINE. . . . (42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:KSA is OFF-LINE.
Note the following key points regarding the preceding excerpt: v The monitoring server appends the KSA product code to the server name to form a unique name (SERVER5B:KSA) for this instance of
221
v v v v
Monitoring Agent for mySAP. This unique name enables you to distinguish multiple monitoring products that might be running on SERVER5B. The log shows when the agent started (ON-LINE) and later stopped (OFF-LINE) in the environment. For the sake of brevity an ellipsis (...) represents the series of trace log entries that were generated while the agent was running. Between the ON-LINE and OFF-LINE log entries, the agent was communicating with the monitoring server. The ON-LINE and OFF-LINE log entries are always available in the trace log. All trace levels that are described in Setting RAS trace parameters provide these entries.
On Windows, you can use the following alternate method to view trace logs: 1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli Monitoring Service. The Manage Tivoli Enterprise Monitoring Services window is displayed. 2. Right-click a component and select Advanced > View Trace Log in the pop-up menu. The program displays the Select Log File window that lists the RAS1 logs for the monitoring agent. 3. Select a log file from the list and click OK. You can also use this viewer to access remote logs. Note: The viewer converts timestamps in the logs to a readable format.
Setting RAS trace parameters

Objective
Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules.
Background information
The Monitoring Agent for mySAP uses RAS1 tracing and generates the logs described in Table 12 on page 220. The default RAS1 trace level is ERROR. RAS1 tracing has control parameters to manage to the size and number of RAS1 logs. Use the procedure described in this section to set the parameters. Note: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost.
Before you begin

See Overview of log file management on page 219 to ensure that you understand log rolling and can reference the correct log files when you managing log file generation.
After you finish

Monitor the size of the logs directory. Default behavior can generate a total of 45 to 60 MB for each agent that is running on a computer. For example, each mySAP system that you monitor could generate 45 to 60 MB of log data. See the Procedure section to learn how to adjust file size and numbers of log files to prevent logging activity from occupying too much disk space.
222
Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files which are pruned automatically, other log types can grow indefinitely, for example, the logs in Table 12 on page 220 that include a process ID number (PID). Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
Procedure
Specify RAS1 trace options by changing trace parameters in a control file. There are two types of control files: v Default control files that contain parameters to be used when a new instance of the agent is configured v Instance control files that contain parameters to be used for an already configured instance of the agent The control file names and locations are as follows: v Windows Location: install_dir\tmaitm6 Default file: KSAENV Instance specific file: KSAENV_3-character-id v UNIX Location install_dir/config Default file: sa.ini Instance specific file: sa_3-character-id.config When changing trace parameters to collect more detailed diagnostic information, change the instance specific control file. Use one of the following methods to modify trace options: v Manually edit the configuration file to set trace logging 1. Open the trace options file: On Windows, open the install_dir\tmaitm6\KSAENV_3-character-ID file. On UNIX systems, open the install_dir/config/sa_3-characterID.config file. 2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. For example, if you want detailed trace logging, set the Maximum Tracing option: On Windows
KBB_RAS1=ERROR (UNIT:ksa ALL) (UNIT:kra ALL)
On UNIX systems
export KBB_RAS1=ERROR (UNIT:ksa ALL) (UNIT:kra ALL)
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files: Edit the following parameters to adjust the number of rolling log files and their size. - MAXFILES: the total number of files that are to be kept for all startups of a given program. Once this value is exceeded, the oldest log files are discarded. Default value is 9.
223
- LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5. IBM Software Support might guide you to modify the following parameters: - COUNT: the number of log files to keep in the rolling cycle of one program startup. Default value is 3. - PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1. Note: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost. 4. Restart the monitoring agent so that your changes take effect. v (Windows only) Use the graphical user interface to set trace options 1. Open the Manage Tivoli Enterprise Monitoring Services window. 2. Right-click the icon for the monitoring agent whose logging you want to modify. 3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed. 4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string. The selections are as follows: No error tracing. KBB_RAS1=-none General error tracing. KBB_RAS1=ERROR Intensive error tracing. KBB_RAS1=ERROR (UNIT:ksa ALL) Maximum error tracing. KBB_RAS1=ERROR (UNIT:ksa ALL) (UNIT:kra ALL) Note: As this example shows, you can set multiple RAS tracing options in a single statement. Modify the value for Maximum Log Size Per File (MB) to change the log file size (changes LIMIT value). Modify the value for Maximum Number of Log Files Per Session to change the number of logs files per startup of a program (changes COUNT value). Modify the value for Maximum Number of Log Files Total to change the number of logs files for all startups of a program (changes MAXFILES value). (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you diagnose communications and connectivity problems between the monitoring agent and the monitoring server.
5. 6. 7.
8.
Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space. 9. Click OK. You see a message reporting a restart of the monitoring agent so that your changes take effect.
224
Enabling and disabling RFC tracing

Objective
Pinpoint a mySAP RFC problem by setting detailed tracing of all RFC calls from the Monitoring Agent for mySAP (RFC client) to the mySAP system (RFC server).
Background information
The Monitoring Agent for mySAP uses RFC tracing and generates logs described below. New RFC trace logs are created each time an instance of the agent starts. The RFC trace logs are located on the computer that hosts the agent in the directory in which the agent start command is issued: v Windows: The trace log is created in \WINDOWS\System32 where the agent runs as a service. v UNIX: The trace log is created in install_dir/bin if you use the ./itmcmd command. Use this procedure to set RFC trace parameters. The RFC trace logs are named as follows:
rfcpid_threadid.trc
Where: pid threadid Thread id For example:

rfc02536_00420.trc
Process ID of the mySAP agent executable (ksaagent)
IBM Software Support applies specialized knowledge to analyze trace logs to determine the source of problems.
Before you begin

RFC tracing is turned off by default. Turn RFC tracing on temporarily while you are troubleshooting an RFC problem.
After you finish

Because trace logs can consume a large amount of hard disk space, turn off detailed logging when you complete an analysis of RFC trace logs. Monitor the size of the RFC trace log directory to prevent RFC trace activity from occupying too much hard disk space. Regularly prune the trace log files because they can grow indefinitely.
Procedure
To enable or disable RFC tracing use one of the following options. Option one: Reconfigure the agent: Perform the following steps to enable RFC tracing for the Monitoring Agent for mySAP. v Windows: 1. In the Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed.
225
2. Right-click the row that contains the name of the monitoring agent for which you want to enable RFC tracing. 3. Select Reconfigure. 4. Click OK in the first and second configuration windows without changing any settings. 5. In the third configuration window, do one of the following: Select the RFC Trace check box to enable tracing. or Clear the RFC Trace check box to disable tracing. 6. Click OK. At this point the agent is reconfigured and stopped. 7. Restart the agent from the Manage Tivoli Enterprise Monitoring Services window. A restart is necessary for the setting takes effect. v UNIX: 1. Go to the install_dir/bin directory. 2. Run the following command:
./itmcmd config -A -o Identifier sa
Where: Identifier Unique system identifier for the agent 3. For all of the configuration prompts, enter NL, without changing the settings you already configured. 4. At the RFC Trace Flag: prompt, enter one of the following: 1 to enable tracing 0 to disable tracing Option Two: Manually edit the configuration file to modify the SAPTRACE environment variable (UNIX only): You can enable or disable RFC tracing by setting the following environment variable: SAPTRACE. Set the environment variable as follows on UNIX: 1. Open the following configuration file: install_dir/config/sa_3-characterID.config 2. Edit the line that begins with SAPTRACE= to set RFC trace preferences as follows: v Set SAPTRACE to 0 to disable RFC Trace. (default) v Set SAPTRACE to 1 to enable RFC Trace. 3. Restart the monitoring agent so that your changes take effect.
RFC trace log problems

Table 13 contains problems and solutions for RFC trace log problems that might occur with the Monitoring Agent for mySAP.
Table 13. Trace log problems Problem RFC trace logs are filling up %SystemRoot%\system32 Solution Trace logs can consume a large amount of hard disk space. Turn on RFC tracing only when you are trying to debug a problem. When you complete an analysis, turn off detailed logging and store the trace logs in another file system.
226
Table 13. Trace log problems (continued) Problem Clicking View RFC Trace in the configuration window displays the wrong RFC trace log. Solution The View RFC Trace option displays the RFC trace log with the most recent timestamp. If you are running more than one instance of the Monitoring Agent for mySAP on the same host, a more recent trace log associated with the other agent instance might be displayed. To avoid displaying the wrong file, turn on the RFC trace option for one Monitoring Agent for mySAP at a time when agents are running on same computer. Use a text editor to view the trace logs manually. The procedure for launching Monitoring Agent for mySAP: Trace Parameters window inSetting RAS trace parameters on page 222 fails. This problem occurs when the trace options file is missing. You can correct the problem as follows: 1. Create a text file with the following path name: v On Windows: install_dir\tmaitm6\KSAENV_3-character-id.config v On UNIX: install_dir/config/sa_3-character-id.config 2. Copy the following configuration setting into the file: v On Windows: KBB_RAS1=ERROR KBB_VARPREFIX=% KBB_RAS1_LOG=<install_dir>\tmaitm6\logs / \%(computername)_sa_%(SAPSYSTEMNAME)_ksaagent_%(sysutcstart) / -.log INVENTORY=<install_dir>\tmaitm6\logs\ / %(computername)_sa_%(SAPSYSTEMNAME)_ksaagent. / inv COUNT=03 LIMIT=5 PRESERVE=1 MAXFILES=9 Note: If you installed the product in a directory path other than the default, use that directory path instead of C:\IBM\ITM. v On UNIX systems: KBB_RAS1=ERROR KBB_VARPREFIX=% KBB_RAS1_LOG=%(CTIRA_LOG_PATH)/<hostname>_sa_%(SAPSYSTEMNAME) \ _%(syspgm)_%(sysutcstart)-.log INVENTORY=%(CTIRA_LOG_PATH)/ \ <hostname>_sa_%(SAPSYSTEMNAME)_%(syspgm).inv COUNT=03 LIMIT=5 \ PRESERVE=1 MAXFILES=9 Note: If you installed the product in a directory path other than the default, use that directory path instead. 3. Save your changes. 4. Repeat the Setting RAS trace parameters on page 222 procedure. The Tivoli Enterprise Monitoring Server: Trace Parameters window is displayed.
Problems and workarounds

The following sections provide symptoms and workarounds for problems that might occur with the Monitoring Agent for mySAP: v Installation and configuration problem determination on page 228 v Agent problem determination on page 232 v Tivoli Enterprise Portal problem determination on page 234 v Workspace problem determination on page 235 v Situation problem determination on page 237 v Take Action command problem determination on page 240
227
Note: You can resolve some problems by ensuring that your system matches the system requirements listed in Chapter 2, Requirements and configuration for the monitoring agent, on page 5. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
Installation and configuration problem determination

This section provides tables that show solutions for problems related to the installation, configuration, and uninstallation. Some of these problems are related to the operating system on which the agent is running. Other problems are specific to installation and configuration of the Monitoring Agent for mySAP.
Table 14. Problems and solutions for installation and configuration for agents that run on UNIX and Windows systems Problem After upgrading to IBM Tivoli Monitoring, you do not have all of the functionality that IBM Tivoli Monitoring offers. Solution You might need to apply fix packs to Candle, Version 350, agents.Fix packs for Candle, Version 350, are delivered as each monitoring agent is upgraded to IBM Tivoli Monitoring. If you do not upgrade the monitoring agent to IBM Tivoli Monitoring, the agent continues to work. However, you must upgrade to have all the functionality that IBM Tivoli Monitoring offers. Note: The IBM Tivoli Monitoring download image or CD provides application fix packs for the monitoring agents that are installed from that CD (for example, the agents for operating systems such as Windows, Linux, UNIX, and i5/OS). The upgrade software for other agents is located on the download image or CDs for that specific monitoring agent, such as the agents for database applications. Presentation files and customized Omegamon The upgrade from version 350 to IBM Tivoli Monitoring handles DE screens for Candle monitoring agents export of the presentation files and the customized Omegamon DE need to be upgraded to a Linux on z/Series screens. system. Non-ASCII characters entered into the configuration window for the monitoring agent do not show up or are not the correct characters. Enter only ASCII characters into these fields.
During the command-line installation on You must exit and restart the installation process. You cannot return UNIX, you choose to install a component that to the list where you selected components to install. When you run is already installed, and you see the the installer again, do not attempt to install any component that is following warning: already installed. WARNING - you are about to install the SAME version of "component" where component is the name of the component that you are attempting to install. On UNIX, while installing the agent from a CD, the following message is displayed and you cannot continue the installation: install.sh warning: unarchive of "/cdrom/unix/cienv1.tar" may have failed This error is caused by low disk space. Although the install.sh script indicates that it is ready to install the agent software, the script considers the size of all tar files, not the size of all the files that are contained within the tar file.Run the df -k command to check whether the file systems have enough space to install agents.
228
Table 14. Problems and solutions for installation and configuration for agents that run on UNIX and Windows systems (continued) Problem Cannot locate the KDCB0_HOSTNAME setting. Solution Go to install_dir/config and edit the sa_3-character-id.config file. Set the KDCB0_HOSTNAME parameter to the IP address of a network card on this computer. If you use multiple network interface cards (NICs), use the Primary IP address of the network interface. You can collect data to analyze this problem as follows: 1. Access the install_dir/config/sa_3-character-id.config file, which is described in Setting RAS trace parameters on page 222. 2. Add the following line: KBB_SIG1=trace dumpoff Agents in the monitoring environment use different communication protocols. For example, some agents have security enabled and others do not. The agent is not able to connect to the Tivoli Enterprise Monitoring Server through a firewall. Configure both the monitoring server and the Warehouse proxy server to accept multiple protocols, as described in the IBM Tivoli Monitoring Installation and Setup Guide. Creating a firewall partition file: The partition file enables an agent to connect to the monitoring server through a firewall. How it works: When the agents start, they search KDCPARTITION.TXT for the following matches: v An entry that matches the partition name OUTSIDE v An entry that also includes a valid external address For more information, see the IBM Tivoli Monitoring Installation and Setup Guide. You successfully migrate a Candle monitoring agent to IBM Tivoli Monitoring, Version 6.1.0. However, when you configure historical data collection, you receive an error message that includes the following: Attribute name may be invalid, or attribute file not installed for warehouse agent. The monitoring agent does not start in a non-ASCII environment. Copy the attribute files for the upgraded Candle monitoring agent to install_dir\tmaitm6\attrlib on the computer where you have installed the Warehouse Proxy. The Warehouse Proxy must be able to access the short attribute names for tables and columns. That way, if the longer versions of these names exceed the limits of the Warehouse database, the shorter names can be substituted.
The Monitoring Agent for mySAP repeatedly restarts.
Check the agent configuration to ensure that all of the values are correctly represented. To view these parameters, go to the Manage Tivoli Enterprise Monitoring Services window, select the agent instance, and click Reconfigure. In the subsequent windows, review and modify configuration parameters as needed. When you have problems with browse settings, perform the following steps: 1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed. 2. Right-click the Windows agent and select Browse Settings. A text window is displayed. 3. Click Save As and save the information in the text file. If requested, you can forward this file to IBM Software Support for analysis.
Browse settings problems: how to diagnose
229
Table 14. Problems and solutions for installation and configuration for agents that run on UNIX and Windows systems (continued) Problem Solution A message similar to Unable to find running If a message similar to Unable to find running CMS on CMS on CT_CMSLIST in the log file is CT_CMSLIST is displayed in the Log file, the agent cannot connect displayed. to the monitoring server. Confirm the following points: v Do multiple network interface cards (NICs) exist on the system? v If multiple NICs exist on the system, find out which one is configured for the monitoring server. Ensure that you specify the correct host name and port settings for communication in the IBM Tivoli Monitoring environment. Error counts are summary report Portal, however, displayed in the displayed in the situation in the Tivoli Enterprise error messages are not situation detail report. Check the timestamp for the reports. If you have set up historical data collection for the situation summary report, also set up historical data collection for the situation detail report. Do not close or modify this window. It is part of the installation process and is dismissed automatically.
While you are using the remote deployment feature to install the Monitoring Agent for mySAP, an empty command window is displayed on the target computer. This problem occurs when the target of remote deployment is a Windows computer. (See the IBM Tivoli Monitoring Installation and Setup Guide for more information about the remote deployment feature.)
The removal of a monitoring agent fails when This problem might occur when you attempt the remote removal you use the remote removal process in the process immediately after you have restarted the Tivoli Enterprise Tivoli Enterprise Portal desktop or browser. Monitoring Server. You must allow time for the monitoring agent to refresh its connection with the Tivoli Enterprise Monitoring Server before you begin the remote removal process. When you edit the configuration for an existing monitoring agent, the values displayed are not correct. The original configuration settings might include non-ASCII characters. These values were stored incorrectly and result in the incorrect display. Enter new values using only ASCII characters.
Table 15. Problems and solutions for installation and configuration of the Monitoring Agent for mySAP Problem Cannot add the Monitoring Agent for mySAP transport request to the buffer through STMS. Cannot enter the full mySAP transport name in the transport system window. Solution Although 20-character transport request names are fully supported by SAP from Basis release 4 and later releases, some release 4.6 transport system windows still have fields that are only 10 characters wide. Import transport by running the addtobuffer command from the command line. See Installing to the mySAP system on page 7.
230
Table 15. Problems and solutions for installation and configuration of the Monitoring Agent for mySAP (continued) Problem Solution
No data is displayed in the Tivoli Check the following issues: Enterprise Portal, though the 1. Check the Monitoring Agent for mySAP log files to see whether there are monitoring agent is started and problems connecting to the Tivoli Enterprise Monitoring Server like those running. mentioned in Agent unable to connect on page 233. 2. Check the agent RAS1 log for RFC or connection errors to the mySAP system. 3. Check the mySAP system syslog to see if the Monitoring Agent for mySAP issued a diagnostic message. This message alerts you to a problem during data collection. 4. If there are no connection problems, check whether the agent has terminated. (Search for the word terminated in the log.) 5. If the agent is not terminated, confirm that you have added application support for the Monitoring Agent for mySAP in the Tivoli Enterprise Monitoring Server as described in IBM Tivoli Monitoring Installation and Setup Guide. Value lists such as report names, monitors, and monitor sets are displayed in English in the following mySAP configuration panels: v Maintain Default Sample Periods v Maintain Log File Names v Maintain ITM Managed Groups Definitions v Select CCMS Monitor Sets and Monitors Text strings such as syslog messages and alert messages do not display correctly in non-English languages. This problem is more likely to occur with double-byte languages. Text in the Monitoring Agent for mySAP configuration panels on a mySAP system do not display in the desired multi-byte language with which you logged on to mySAP. Agent transport errors Set the SAP_CODEPAGE environment variable. See Setting RAS trace parameters on page 222. This is expected. These value lists are presented in English only regardless of the SAP logon language.
Ensure that you logged on to the mySAP system or SAPGUI using a supported language. See page 12for a list of the languages that the Monitoring Agent for mySAP supports. Ensure that you have installed NLS support for the mySAP transport text elements. See Non-Unicode double-byte language support on page 24. v Update the following SAP kernel executables to the latest level: R3trans tp v Verify that the cofile and data transport files have correct authorizations and owners: sapsid:sapsys v Check the syntax of the following commands: tp addtobuffer tp import See Step 3 on page 8 for more information about these commands. v Ensure that the default user IBMMON_AGENT or ZITM_610AUTH roles were created during transport import. See Central User Administration (CUA) on page 17 for requirements.
231
Table 15. Problems and solutions for installation and configuration of the Monitoring Agent for mySAP (continued) Problem Incorrect parameters: v Incorrect SAP hostname, GW hostname, GW port, user ID, password, or client v SAP User ID has incorrect SAP authorizations v SAP user specified does not exist v SAP user password is incorrect v SAP user is locked (disabled) Table 16. General problems and solutions for uninstallation Problem On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire environment. Solution Be sure that you follow the general uninstallation process described in the IBM Tivoli Monitoring Installation and Setup Guide: 1. Uninstall monitoring agents first. 2. Uninstall IBM Tivoli Monitoring. The way to remove inactive managed systems (systems with a status of OFFLINE) from the enterprise Navigation tree in the portal is not obvious. When you want to remove a managed system from the Navigation tree, right-click the item that you want to remove, and select Remove managed system. Note: The OS agent must be installed on the target computer in order for this function to work. Solution These problems are based on the RFC parameters connection. Change the parameter that is in error. Ensure that the default user IBMMON_AGENT or ZITM_610auth roles were created during transport import. See Central User Administration (CUA) on page 17 for requirements.
Agent problem determination

Table 17 contains problems that might occur with the Monitoring Agent for mySAP. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
Table 17. Agent problems and solutions Problem A problem can arise when you run multiple agents on one computer and want them to communicate with multiple monitoring servers, as described in this example: v Agents are running on computer and communicating with a Tivoli Enterprise Monitoring Server, called TEMS1. v You install a new agent on the same computer and you want this agent to communicate with a different monitoring server, called TEMS2. v When you configure the new agent to communicate with TEMS2, all the existing agents are re-configured to communicate with TEMS2. Solution You must reconfigure the previously existing agents to restore their communication connection with TEMS1. For example, you can right-click the row for a specific agent in the Manage Tivoli Monitoring Services, and select Reconfigure. See the IBM Tivoli Monitoring Installation and Setup Guide for more information on reconfiguration.
232
Table 17. Agent problems and solutions (continued) Problem Agent unable to connect: The agent is started, but no data is reported to the Tivoli Enterprise Monitoring Server. The log file includes the following error: Unable to find running CMS on CMSLIST or Endpoint unavailable Solution This error message means that the agent cannot connect to the computer where the Tivoli Enterprise Monitoring Server is running. The reason might be any one of the following: Computer where the Tivoli Enterprise Monitoring Server is running is down Ping the computer where the Tivoli Enterprise Monitoring Server is running and make sure that it is up and running. Tivoli Enterprise Monitoring Server is not running If the Tivoli Enterprise Monitoring Server is not running, recycle the Tivoli Enterprise Monitoring Server and verify whether the agent is connecting. Multiple NIC Cards on the computer where the Tivoli Enterprise Monitoring Server is running. If multiple NICs are installed on the computer where the Tivoli Enterprise Monitoring Server is running, identify the Primary NIC and use the hostname or IP address. Verify that the Tivoli Enterprise Monitoring Server has been configured with the Primary NICs IP address or hostname. If you are using hostname, make sure that /etc/hosts has a valid entry for the Primary NICs host name and its IP address. On the Tivoli Enterprise Monitoring Server set the KDCB0_HOSTNAME variable to the primary IP address of the computer. Use the same address to configure the agent. To connect to the Tivoli Enterprise Monitoring Server, configure the agent with Primary NICs IP address or host name of the computer where the Tivoli Enterprise Monitoring Server is running. While configuring the agent, make sure that the port number that you are connecting to is correct. If you are not using the default port number, make sure that you are using the same port number used in Tivoli Enterprise Monitoring Server. For more information, see the IBM Tivoli Monitoring Installation and Setup Guide. Agent is behind the Firewall If you use a firewall, identify whether you have any one of the following scenarios: v Hub monitoring server INSIDE, and agents OUTSIDE v Hub and remote monitoring servers INSIDE, agents OUTSIDE v Hub monitoring server INSIDE, remote monitoring server and agents OUTSIDE See Creating a firewall partition file on page 229 for information about the KDC_PARTITION file that enables communication across a firewall. For additional information, see the IBM Tivoli Monitoring Installation and Setup Guide. Connecting to the monitoring server through a Virtual Private Network (VPN) In some cases, the agent or a remote monitoring server needs to connect to the hub monitoring server through a VPN. You must configure the communication channel (pipe) to be ephemeral, as in the following example: KDC_FAMILIES=ip.pipe port:port_number ephemeral:y ip use:n sna use:n
233
Table 17. Agent problems and solutions (continued) Problem On UNIX, you want to have multiple instances of Monitoring Agent for mySAP running on the same computer, but communicating with different Tivoli Enterprise Monitoring Servers. Solution Enable multiple instances as follows: 1. Open each instance configuration file (sa_3-character-id.config) in install_dir/config. 2. Insert the following definition for CT_CMSLIST: export CT_CMSLIST=ip.pipe: hostname_or_IP_address_of_TEMS 3. Insert the following definition for KDC_FAMILIES: export KDC_FAMILIES=ip.pipe port: port_number ip use:n ip.spipe use:n sna use:n Data collection stops or runs sluggishly on your SAP systems with Oracle databases. When running the /IBMMON/ITM_* transactions, you get an error indicating that the transaction is not valid. The Monitoring Agent for mySAP cannot connect to the mySAP system. The agent is started but no :Ins or :Sys managed system names are displayed in the Tivoli Enterprise Portal Navigator tree. The log file includes the following lines: Unable to find the Central Instance See Oracle data collection on page 9. Preface all /IBMMON/ITM_* transactions with /n or /o.
Ensure that you configured the agent with the correct mySAP logon information (user ID, password, client) Reconfigure, and restart. Check the RAS1 log for connection errors. A RAS1 error such as the following indicates that the agent could not logon on with the connection parameters specified during agent configuration: Failure on call to /IBMMON/ITM_VERIFY_LOGON. Verify that all the values are correct. See Configuring the Monitoring Agent for mySAP on page 10. This occurs when the Monitoring Agent for mySAP cannot connect to a remote mySAP system. Ensure that you configured the agent with the correct mySAP logon information (user ID, password, client) Reconfigure, and restart. To remove the agent from the Navigator tree, stop the agent if it is still running, and remove Offline Entry from the Tivoli Enterprise Portal Server. Slashes in attribute names must be escaped with an additional slash for the Tivoli Enterprise Portal to recognize them. For example, R/3_Alerts.MTE_Class must be represented as R//3_Alerts.MTE_Class in the launch definition. To do this, when creating a launch definition, use the GUI to select an attribute from the list. Or, type in the attribute names manually and escape the /.
The Monitoring Agent for mySAP shows up in the Tivoli Enterprise Portal Navigator tree with the wrong hostname in the agent name: SID-hostname. The hostname is the name of the agent hostname rather than the SAP DB hostname.
Custom launch definitions that you create report an error that a mySAP agent attribute name cannot be evaluated.
Tivoli Enterprise Portal problem determination

Table 18 on page 235 contains problems that might occur with the Tivoli Enterprise Portal. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
234
Table 18. Tivoli Enterprise Portal problems and solutions Problem Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal. Solution The column, Sort By, Group By, and First/Last functions are not compatible with the historical data collection feature. Use of these advanced functions make a query ineligible for historical data collection. Even if data collection has been started, you cannot use the time span feature if the query for the chart or table includes any column functions or advanced query options (Sort By, Group By, First/Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. See the IBM Tivoli Monitoring Administrators Guide the Tivoli Enterprise Portal online Help for information on the Historical Data Collection function. No data is displayed in the Tivoli Enterprise Portal. There are several solutions: v Check for alerts generated by IBM Tivoli Monitoring. The Monitoring Agent for mySAP creates these alerts to indicate problems with the agent. v Check the SAP Syslog. The Monitoring Agent for mySAP writes diagnostic messages to this log file when a problem occurs. If the agent transport is not installed on the target mySAP system, install the agent to the mySAP system. See Installing to the mySAP system on page 7. If the agent could not connect to the mySAP system, you might need to change the RFC connection parameters. See mySAP RFC connections on page 21. When you right-click on a There is no solution for this problem. workspace table view and click Launch, the screen that is displayed is missing the (E) mnemonic on the Evaluate option for double-byte languages. When viewing the Information There is no solution for this problem. The remaining text is displayed in the Center, the Welcome to the translated language. IBM Tivoli Monitoring Information Center panel is not translated into non-English languages.
Workspace problem determination

Table 19 contains problems that might occur with workspaces. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
Table 19. Workspace problems and solutions Problem You see the following message: KFWITM083W Default link is disabled for the selected object; please verify link and link anchor definitions. The name of the attribute does not display in a bar chart or graph view. Solution You see this message because some links do not have default workspaces. Right-click the link to access a list of workspaces to select. When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until there is enough space to display all characters of the attributes name.
235
Table 19. Workspace problems and solutions (continued) Problem Historical data is not displayed though you started collection of historical data. Solution Managing options for historical data collection: v Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. See the IBM Tivoli Monitoring Administrators Guide for information on managing this feature including how to set the interval at which data is collected. By setting a more frequent interval for data collection you reduce the load on the system incurred every time data is uploaded. v You use the Summarization and Pruning monitoring agent to collect specific amounts and types of historical data. Be aware that historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 a.m. daily. At that point, data is visible in the workspace view. See the IBM Tivoli Monitoring Administrators Guide to learn how to modify the default collection settings. No CCMS alerts show in the Alerts workspace (If CCMS alert collection takes too long you might not get any alerts.) If errors occur in the mySAP system, the Monitoring Agent for mySAP experiences the same errors. Do the following: v Correct the errors in the mySAP system. Look at the mySAP system to determine if CCMS is responding. Logon to the mySAP system and run RZ20 to see if CCMS is responding. If CCMS is not responding contact SAP support or access SAP online support tools at service.sap.com. v Agent CCMS collection timeout values might need to be increased. The agent times out if it cannot collect the data in 2 minutes. Contact IBM Software Support for instructions on how to temporarily increase the CCMS data collection time out setting for diagnostic purposes. Setting this value higher affects the responsiveness of the Monitoring Agent for mySAP. v Ensure that SAPCCMSR agents are working correctly. v Ensure that the CCMS Monitors and Monitor tree elements are selected with agent config /IBMMON/ITM_ALERTS. All of the rows of data you expected to see in a workspace are not displayed. v If it is a time span workspace, check that the time span is set to the proper value. v Check for alert 9911, Excessive data collected for workspace, generated by IBM Tivoli Monitoring. This alert means that the number of data rows collected exceeds the maximum number of rows that the agent is configured to send to the Tivoli Enterprise Portal Server. It tells you how many rows of data were not returned. To modify the maximum row setting, see Maintain ITM generated alerts on page 22. Increasing the maximum number of data rows can have a negative impact on agent and Tivoli Enterprise Portal Server performance. v SeeVerifying the prerequisites for data collection on page 9 for more information. Timestamps that are displayed in the workspaces See Alert timestamps on page 40. do not match the timestamps you are expecting. No log data appears in the workspaces that display log data, for example, the Database Logs workspace. Ensure that the log files and their locations are properly configured for the agent to monitor. See Maintain log file names on page 22.
236
Table 19. Workspace problems and solutions (continued) Problem No data appears in the Gateway Statistics workspace. Solution Enable Gateway Statistics by selecting the Enable Gateway Statistics link or Reset Gateway Statistics link from within the Gateway Statistics workspace. Note: Gateway statistics are intended to be enabled for a short period of time during specific analysis. Enabling gateway statistics for a long period of time can result in the gateway statistics values becoming too large to report.
No applicable data is displayed in a workspace The Monitoring Agent for mySAP was unable to find any data table. that met the query parameters. This can occur in the following cases: v There has been no activity for a function within the real-time interval in which the agent is looking. If the view supports timespans, try a longer timespan interval. v The :Grp managed system is not configured to report the type of data requested. This is a configuration limitation based on how you defined the group in the mySAP system. No data is displayed in a top level workspace for managed system names ending in :Sys. This is a current limitation of the Tivoli Enterprise Portal Server. Only one workspace can be assigned to a top level managed system, so all managed system names (:Ins, :Sys or :Grp) share the same workspace. This workspace contains instance specific views that are not populated when displayed for :Sys managed system names.
Situation problem determination

This section provides information about both general situation problems and problems with the configuration of situations. See the IBM Tivoli Monitoring Problem Determination Guide for more information about problem determination for situations.
General situation problems

Table 20 contains problems that might occur with specific situations.
Table 20. Specific situation problems and solutions Problem You want to change the appearance of situations when they are displayed in a Workspace view. Solution 1. Right-click an item in the Navigation tree. 2. Select Situations in the pop-up menu. The Situation Editor window is displayed. 3. Select the situation that you want to modify. 4. Use the Status menu in the lower right of the window to set the status and appearance of the Situation when it triggers. Note: This status setting is not related to severity settings in IBM Tivoli Enterprise Console. Monitoring activity requires too much disk space. Check the RAS trace logging settings that are described in Setting RAS trace parameters on page 222. For example, trace logs grow rapidly when you apply the ALL logging option.
237
Table 20. Specific situation problems and solutions (continued) Problem A formula that uses mathematical operators appears to be incorrect. For example, if you are monitoring Linux, a formula that calculates when Free Memory falls under 10 percent of Total Memory does not work: LT #Linux_VM_Stats.Total_Memory / 10 If you are running a Version 350 Monitoring Agent for mySAP and you choose to alter the views to include a Version 610 UNICODE attribute, be aware that data for this attribute is not displayed and you see a blank column in this view. Situations that you create display the severity UNKNOWN in the IBM Tivoli Enterprise Console. Solution This formula is incorrect because situation predicates support only logical operators. Your formulas cannot have mathematical operators. Note: The Situation Editor provides alternatives to math operators. Regarding the example, you can select % Memory Free attribute and avoid the need for math operators.
Access the database detail. In the release section change the version setting for the agent from 610 to 350. To enable Unicode and other features, upgrade the monitoring agent to IBM Tivoli Monitoring, Version 6.1.0.
For a situation that is not mapped to have the correct severity in the Tivoli Enterprise Console, ensure that one of the following is true: 1. If an entry is found in the tecserver.txt file for the situation and SEVERITY is specified, the value specified is used. OR 2. Add a severity suffix to the name of the situation. If the situation name ends with a standard severity code, IBM Tivoli Enterprise Console derives the severity from the name. For example, a situation name with the suffix _Warn or _Warning has the WARNING severity in IBM Tivoli Enterprise Console. The suffix _Cri or _Critical is displayed as CRITICAL severity.
You see the 'Unable to get attribute name' error in the Tivoli Enterprise Monitoring Server log after creating a situation.
Ensure that the agent attribute files are installed on the Tivoli Enterprise Monitoring Server. The following example shows a typical log entry when you have this problem: (4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \ Unable to get attribute name for tablename/column \ <UAG524400.UA4>. Ignored.
When you use a long process name in the situation, the process name is truncated.
Truncation of process names in the portal display is the expected behavior. 64 bytes is the maximum name length.
Problems with situation configuration

Table 21 through Table 23 on page 240 contain problems that might occur with situations. This section provides information for problem determination for agents. Be sure to consult the IBM Tivoli Monitoring Problem Determination Guide for more general problem determination information.
Table 21. Problems with configuring situations that you solve in the Situation Editor Problem Solution
Note: To get started with the solutions in this section, perform these steps: 1. Launch the Tivoli Enterprise Portal. 2. Click Edit > Situation Editor. 3. In the tree view, choose the agent that has the situation you want to modify. 4. Select the situation in the list. The Situation Editor view is displayed.
238
Table 21. Problems with configuring situations that you solve in the Situation Editor (continued) Problem Solution
The situation for a specific agent is Open the Situation Editor. Access the All managed servers view. If the situation not visible in the Tivoli Enterprise is absent, confirm that application support for Monitoring Agent for mySAP Portal. has been added to the monitoring server. If not, add application support to the server, as described in the IBM Tivoli Monitoring Installation and Setup Guide. The monitoring interval is too long. The situation did not activate at startup. Access the Situation Editor view for the situation that you want to modify. Check the Sampling interval area in the Formula tab. Adjust the time interval as needed. Manually recycle the situation as follows: 1. Right-click the situation and select Stop Situation. 2. Right-click the situation and select Start Situation. Note: You can permanently avoid this problem by placing a check mark in the Run at Startup option of the Situation Editor view for a specific situation. The situation is not displayed. Click the Action tab and check whether the situation has an automated corrective action. This action can occur directly or through a policy. The situation might be resolving so quickly that you do not see the event or the update in the graphical user interface.
A situation event has not occurred Check the logs, reports, and workspaces. even though the predicate has been properly specified. A situation fires on an unexpected managed object. The product did not distribute the situation to a managed system. The situation does not fire. Incorrect predicates are present in the formula that defines the situation. For example, the managed object shows a state that normally triggers a monitoring event, but the situation is not true because the wrong attribute is specified in the formula. Confirm that you have distributed and started the situation on the correct managed system. Click the Distribution tab and check the distribution settings for the situation. In the Formula tab, analyze predicates as follows: 1. Click the fx icon in the upper-right corner of the Formula area. The Show formula window is displayed. a. Confirm the following details in the Formula area at the top of the window: v The attributes that you intend to monitor are specified in the formula. v The situations that you intend to monitor are specified in the formula. v The logical operators in the formula match your monitoring goal. v The numerical values in the formula match your monitoring goal. b. (Optional) Click the Show detailed formula check box in the lower left of the window to see the original names of attributes in the application or operating system that you are monitoring. c. Click OK to dismiss the Show formula window. 2. (Optional) In the Formula area of the Formula tab, temporarily assign numerical values that immediately trigger a monitoring event. The triggering of the event confirms that other predicates in the formula are valid. Note: After you complete this test, you must restore the numerical values to valid levels so that you do not generate excessive monitoring data based on your temporary settings. Table 22. Problems with configuration of situations that you solve in the workspace area Problem Situation events are not displayed in the Events Console view of the workspace. Solution Associate the situation with a workspace. Note: The situation does not need to be displayed in the workspace. It is sufficient that the situation is associated with any workspace.
239
Table 22. Problems with configuration of situations that you solve in the workspace area (continued) Problem You do not have access to a situation. Solution Note: You must have administrator privileges to perform these steps. 1. Select Edit > Administer Users to access the Administer Users window. 2. In the Users area, select the user that has the privileges you want to modify. 3. In the Permissions tab, Applications tab, and Navigator Views tab, select the permissions or privileges that correspond to the users role. 4. Click OK. A managed system seems to be offline. 1. Select Physical View and highlight the Enterprise Level of the Navigator tree. 2. Select View > Workspace > Managed System Status to see a list of managed systems and their status. 3. If a system is offline, check network connectivity and status of the specific system or application. Table 23. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services window Problem After an attempt to restart the agents in the Tivoli Enterprise Portal, the agents are still not running. The Tivoli Enterprise Monitoring Server is not running. The managed objects you created are firing on incorrect managed systems. Solution Check the system status and check the appropriate IBM Tivoli Monitoring logs.
Check the system status and check the appropriate IBM Tivoli Monitoring logs. Check the managed system distribution on both the situation and the managed object settings sheets.
Take Action command problem determination

Table 24 contains general problems that might occur with Take Action commands. When each Take Action command runs it generates the log files listed in Table 12 on page 220. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information.
Table 24. Take Action commands problems and solutions Problem Take Action commands might require several minutes to complete. Solution Allow several minutes. If you do not see a pop-up message advising you of completion, try to run the command manually. If you are unable to perform the Take Action command manually, see IBM Tivoli Monitoring Problem Determination Guide for general information on troubleshooting the Take Action command.
240
Support information
If you have a problem with your IBM software, you have the following options for obtaining support for software products: v Searching knowledge bases v Obtaining fixes on page 242 v Receiving weekly support updates on page 242 v Contacting IBM Software Support on page 242 v Using IBM Software Services for Tivoli on page 244
Searching knowledge bases

You can search the available knowledge bases to determine whether your problem was already encountered and is already documented.
Searching the information center

Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper. The documentation CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: http://www.ibm.com/software/tivoli/library Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click M to access all of the IBM Tivoli Monitoring product manuals.
Searching the Internet

If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. The IBM Software Support Web site provides the latest information about known product limitations and workarounds in the form of technotes for your product. You can view this information at the following Web site: http://www.ibm.com/software/support To search for information on IBM products through the Internet (for example, on Google), be sure to consider the following types of documentation: v IBM technotes v IBM downloads v IBM Redbooks v IBM developerWorks v Forums and newsgroups
241
Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes are available for your IBM software product, follow these steps: 1. Go to the Software support Web site at http://www.ibm.com/software/ support. 2. Click the Download tab. 3. Select the operating system in the Operating system menu. 4. Type search terms in the Enter search terms field. 5. As appropriate, use other search options to further define your search. 6. Click Search. 7. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are available, see the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/ handbook.html.
Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at http://www.ibm.com/software/ support. 2. Click My account in the upper right corner of the page. 3. Click Subscribe to IBM e-news. (If you have already subscribed and want to modify your subscription preferences, click Modify subscriptions and follow the instructions on screen.) 4. Follow the instructions on screen to provide the following data: v Your personal contact information. v Your areas of interest. v The types of subscriptions and regional versions that you want to receive. 5. Review the subscription confirmation to confirm your settings.
Contacting IBM Software Support

IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows, or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online Go to the Passport Advantage Web site at http://www.lotus.com/ services/passport.nsf/ WebDocs/Passport_Advantage_Home and click How to Enroll. By phone For the phone number to call in your country, go to the IBM Software
242
Support Web site at http://techsupport.services.ibm.com/guides/ contacts.html and click the name of your geographic region. v For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at https://techsupport.services.ibm.com/ssr/ login. v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries, z/Series, and other support agreements, go to the IBM Support Line Web site at http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006. v For IBM eServer software products (including, but not limited to, DB2 and WebSphere products that run in z/Series, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web site http://www.ibm.com/servers/eserver/techsupport.html. If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location. To 1. 2. 3. contact IBM Software support, follow these steps: Determining the business impact Describing problems and gathering information Submitting problems on page 244
Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria: Severity 1 The problem has a critical business impact. You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Severity 2 The problem has a significant business impact. The program is usable, but it is severely limited. Severity 3 The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unavailable. Severity 4 The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.
Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred?
243
v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can you re-create the problem? If so, what steps were performed to re-create the problem? v Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, and so on. v Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem. See Gathering product information for IBM Software Support on page 217 for further tips for gathering information for IBM Software Support.
Submitting problems
You can submit your problem to IBM Software Support in one of two ways: Online Click Submit and track problems on the IBM Software Support site at http://www.ibm.com/software/support/probsub.html. Type your information into the appropriate problem submission form. By phone For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook at http://techsupport.services.ibm.com/ guides/contacts.html and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.
Using IBM Software Services for Tivoli

You can use IBM Software Services for Tivoli to get a quick start in implementing your software or to migrate your existing Tivoli-based monitoring environment to the new IBM Tivoli Monitoring technology. Services are provided worldwide by a team of highly skilled consultants with broad architectural knowledge and deep technical skills. Our consultants prepare your staff and assist them in designing, building, deploying, and supporting your IT management solution. For more information about these consulting services and enablement offerings, visit the following Web site: ibm.com/software/tivoli/services/consulting/offerings.html
244
Appendix D. Accessibility
Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to use software products successfully. The major accessibility features in this product enable users to do the following: v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what is displayed on the screen. Consult the product documentation of the assistive technology for details on using those technologies with this product. v Operate specific or equivalent features using only the keyboard. v Magnify what is displayed on the screen. In addition, the product documentation was modified to include the following features to aid accessibility: v All documentation is available in both HTML and convertible PDF formats to give the maximum opportunity for users to apply screen-reader software. v All images in the documentation are provided with alternative text so that users with vision impairments can understand the contents of the images.
Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and are documented by the operating system. Refer to the documentation provided by your operating system for more information.
Magnifying what is displayed on the screen

You can enlarge information on the product windows using facilities provided by the operating systems on which the product is run. For example, in a Microsoft Windows environment, you can lower the resolution of the screen to enlarge the font sizes of the text on the screen. Refer to the documentation provided by your operating system for more information.
245
246
Appendix E. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
247
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating systems. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating system for which the sample programs are written. These examples have not been
248
thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBMs application programming interfaces. If you are viewing this information in softcopy form, the photographs and color illustrations might not appear.
Trademarks
AIX, DB2, developerWorks, eServer, i5/OS, IBM, the IBM logo, IBMLink, iSeries, Lotus, OMEGAMON, Passport Advantage, pSeries, Rational, Redbooks, OS/390, OS/400, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli Enterprise Console, WebSphere, and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel is a registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.
Appendix E. Notices
249
250
Index A
ABAP Dumps attribute group 65 situations 145 system log 156 workspace 36 accessibility xii, 245 action links 34 actions See Take Action commands Active Users attribute group 66 situations 145 workspace 37 agent installation problems 228 performance considerations 237 problem determination 232 trace logs 220 alerts 9911 236 CCMS, selecting 22 ITM generated 22 special 39 timestamps 40 Alerts attribute group 67 situations 146 workspace 38 Application Performance workspace 41 applications supported 6 Archive Monitor attribute group 69 workspace 41 Asynchronous Updates workspace 42 attribute groups ABAP Dumps 65 Active Users 66 Alerts 67 Archive Monitor 69 Batch Data Create 71 Batch Data Create Log 72 Batch Job Logs 75 Batch Jobs 73 Buffer Performance 76 Data Base Detail 79 Data Base Summary 80 Database Logs 82 Developer Traces 82 EDI Files 83 File Systems 84 Gateway Connections 85 Gateway Statistics 87 Instance Configuration 91 Intermediate Documents 95 list of all 64 Lock Entries 97 Logon Group 98 Logon Information 100 more information 63 Number Range Buffer Details 101 Copyright IBM Corp. 2006 attribute groups (continued) Number Range Buffer Summary 102 Operating System and LAN 104 Outputs Request 105 overview 63 Perform Requested Action 108 SAP Office Inbox 108 Saprouter Log 110 Service Response Time 111 Set Default Sample Period 113 Spool Requests 113 System Log 115 System Log Details 116 Topology Information 117 Transaction Performance 117 Transactional RFC 120 Transport Log 122 Transport Objects 122 Transport Requests 123 Transport Steps 125 types 63 Updates Information 127 User Information 128 Work Processes 130 attributes more information 63 overview 63 unicode 63 use 63
B
basic agent monitoring 16 Batch Data Create attribute group 71 situations 146 workspace 42 Batch Data Create Log attribute group 72 workspace 42 batch job COLLECTOR_FOR_PERFORMANCE 9 Batch Job Log workspace 43 Batch Job Logs attribute group 75 Batch Jobs attribute group 73 situations 146 workspace 43 books feedback x online x ordering x see publications xi Buffer Performance attribute group 76 workspace 44 Buffer situations 147 built-in problem determination features 218
251
C
calculate historical data disk space 134 Cancel Job action 160 capacity planning for historical data 134 CCMS centralized reporting 23 CCMS alerts closing 160 timestamps 40 viewing 38 which to report 22 Central User Administration 17 Centralized CCMS reporting 23 client number 12 Close Alert action 160 Close Alert Results workspace 45 Close All Alerts Results workspace 45 collecting data historical 31 COLLECTOR_FOR_PERFORMANCE batch job 9 commands itm config 21 itmcmd agent 13 itmcmd config 10 ksanfy 206 ksapwd 214 ksar3 210 ksar3exe 211 ksar3nfy 207 ksar3pwd 215 non-Unicode 8 sapshcut 20 tacmd addSystem 15 Take Action 159 tp addtobuffer 8, 9, 25 tp import 8, 9, 25 unicode 9 utility 205 components Monitoring Agent for mySAP 2 supported 6 Computing Center Management System See CCMS configuration advanced 15 basic 6 parameters 11 transactions 21 UNIX 10 Windows 10 contacting IBM Software Services for Tivoli 244 contacting support 242 conventions operating system xiii typeface xii creating automation 18 CUA See Central User Administration customer support See support customizing agent behaviors 21 monitoring environment 29 situations 30
D
data collecting 31 trace logs 218 viewing 31 Data Base Detail attribute group 79 Data Base Summary attribute group 80 data collection COLLECTOR_FOR_PERFORMANCE 9 historical 31 Oracle 9 OS Collector 10 prerequisites 9 data provider See agent Data Transfer Information workspace 46 Database Logs attribute group 82 workspace 46 Database situations 149 Database workspace 45 default sample periods, maintaining 22 defining the user 7 Delete Job action 161 Delete situations 150 detecting problems, modifying situation values 30 Developer Traces attribute group 82 workspace 47 Dialog situations 150 directory names, notation xiii Disable Gateway Statistics Results workspace 47 disk capacity planning for historical data 134 disk space requirements 6 double-byte language support 24
E
EDI Files attribute group 83 education see Tivoli technical training xii Enable Gateway Statistics workspace encrypting a password 19 Enqueue Locks workspace 48 environment customizing 29 features 1 real-time monitoring 27 environment variables ksar3 and ksanfy 18 notation xiii events investigating 28 mapping 167 workspaces 28 Excess Memory situations 150 Execute brarchive action 161 47
F
features, Monitoring Agent for mySAP file names, maintaining for logs 22 File Systems attribute group 84 situations 150 workspace 48 1
252
FILE() 19 FILE(file_name) 19 files agent trace 220 installation trace 220 K610_00xxx.ITM 8, 25 K610_00xxxU.ITM 8, 25 K610_DELETE 8, 25 KSAENV 223 ksar3exe 18 other trace log 220 R610_00xxx.ITM 8, 25 R610_00xxxU.ITM 8, 25 R610_DELETE 8, 25 trace logs 218 transport 8 non-Unicode 8, 25 Unicode 8, 25 fixes, obtaining 242
G
Gateway Connections attribute group 85 situations 151 gateway name 12 gateway service 12 Gateway Statistics attribute group 87 workspace 48 gathering support information guidelines for monitoring 7
217
information, additional (continued) Take Action commands 159 workspaces 34 installation advanced 15 basic 6 log file 220 problems 228 to the IBM Tivoli Monitoring system 10 to the mySAP system 7 installing SAP transport 7 to the IBM Tivoli Monitoring system 10 to the mySAP system 7 Instance Configuration attribute group 91 situations 151 workspace 49 instance number 12 Instance Summary workspace 50 interface, user description 3 problem determination for Tivoli Enterprise Portal Intermediate Documents attribute group 95 Internet for product support 241 investigating an event 28 itm config command 21 ITM() 19 itmcmd agent command 13 itmcmd config command 10 ITMK610_00xxx.ITM transport request 9
234
J H
Hide Agent Logon Parms from ITM 13, 18 historical data calculate disk space 134 collecting and viewing 31 disk capacity planning 134 Historical Database workspace 49 Historical Operating System workspace 49 Historical Service Response Time workspace 49 Historical Database workspace 49 Historical Operating System workspace 49 Historical Service Response Time workspace 49 host name 11 job, COLLECTOR_FOR_PERFORMANCE 9
K
K610_00xxx.ITM files 8, 25 K610_00xxxU.ITM 8 K610_00xxxU.ITM files 25 K610_DELETE files 8, 25 knowledge bases for support KSAENV file 223 ksanfy command 206 script 18 variables 18 ksapwd command 214 script 19 ksar3 command 210 script 18 variables 18 ksar3exe command 211 utility 18 ksar3nfy command 207 utility 18 ksar3pwd command 215 utility 19
241
I
IBM Software Services for Tivoli See support IBM Software Support See support IBM Tivoli Enterprise Console event mapping 167 optional product 2 IBM Tivoli Monitoring overview 1 IBMMON_AGENT user ID 16 import options 9 information centers for support 241 information, additional attributes 63 policies 165 procedural 27 situations 141
Index
253
L
language support double-byte 24 non-unicode 24 languages 12 launch definitions, predefined 33 launching the SAPGUI 17 legal notices 247 links, action 34 local management 16 Lock Entries attribute group 97 log files, maintaining names 22 logging agent trace logs 220 built-in features 218 installation log files 220 location and configuration of logs trace log files 218 Login and Logoff situations 152 logon environment variables 18 Logon Group attribute group 98 Logon Groups workspace 50 Logon Information attribute group 100 workspace 50
Number Range Buffer Summary attribute group Number Range Buffer workspace 51 Number Range situations 152
102
O
online publications accessing xi for support 241 Operating System and LAN attribute group 104 workspace 51 operating systems 5 operation of resource, recovering Oracle data collection 9 ordering publications xi OS and LAN situations 152 OS Collector 10 other requirements 6 Output Request action 162 Output Requests attribute group 105 workspace 52 Output situations 153
28
218
M
maintaining default sample periods 22 ITM generated alerts 22 log file names 22 managed groups 22 managed groups, maintaining 22 manuals feedback x online x ordering x see publications xi memory requirements 6 Memory workspace 51 messages, built-in features 218 modifying situation values to detect problems monitor sets, selecting 22 monitoring basic 16 guidelines 7 viewing the real-time environment 27 Monitoring Agent for mySAP components 2 features 1 purposes 27 using 27 monitors, selecting 22 mySAP transport, installing 7 mySAP utilities 15
P
parameters RAS trace 222 password configuration parameter 12 default 7 encrypting 19 ksapwd 19 variable 19 path names notation xiii path names, for trace logs 218 Perform Requested Action attribute group 108 performance considerations 237 policies list of all 165 more information 165 overview 165 predefined 165 R3_Monitor_ABAP_Dumps 165 R3_Monitor_Batch_Jobs 166 R3_Monitor_File_Systems 166 R3_Monitor_Production_Repairs 166 R3_Start_Buffer_Monitoring 166 predefined launch definitions 33 prerequisites for data collection, verifying 9 Private Memory situations 154 Private Mode situations 154 problem determination agents 232 built-in features 218 describing problems 243 determining business impact 243 information centers for 241 installation 228 installation logs 220 knowledge bases for 241 remote deployment 230 RFC trace log 226 situations 237, 238
30
N
Navigator tree for Monitoring Agent for mySAP 33 non-Unicode language support 24 notation environment variables xiii path names xiii typeface xiii Number Range Buffer Details attribute group 101
254
problem determination (continued) submitting problems 244 symptoms and workarounds 227 Take Action commands 240 Tivoli Enterprise Portal 234 uninstallation 228 uninstallation logs 220 workspaces 235 problems and workarounds 227 detecting 30 uninstallation 232 procedures for using Monitoring Agent for mySAP PROMPT(EVERY) 19 PROMPT(ONCE) 19 publications accessing online xi feedback x for support 241 online x ordering x, xi purposes collecting data 31 customizing monitoring environment 29 investigating events 28 monitoring with custom situations 30 problem determination 217 recovering resource operation 28 viewing data 31 viewing real-time monitoring environment 27
RFC trace 13 RFC trace logs location 225 problems 226 RFC tracing disabling 225 enabling 225 RSORAUD0 program
S
27 SAP Basis supported 5 SAP Notes 16083 9 591801 9 713211 9 SAP Office situations 154 SAP Office email utility to send 18 SAP Office Inbox attribute group 108 workspace 53 SAP Router situations 154 SAPGUI launching 17 situations 154 saposcol program 10 SAPPASSWORD variable 18 Saprouter Log attribute group 110 SAProuter Log workspace 53 sapshcut command 20 SAPTRACE variable 226 SAPUSER variable 18 scripts ksanfy 18 ksapwd 19 ksar3 18 ksar3 and ksanfy 18 selecting monitor sets and monitors 22 Service Response situations 154 Service Response Time attribute group 111 workspace 54 services, contacting 244 Set Default Sample Period attribute group setting RAS trace parameters 222 situations ABAP Dumps 145 Active Users 145 Alert 146 Batch Data Create 146 Batch Jobs 146 Buffer 147 Database 149 Delete 150 Dialog 150 Excess Memory 150 File Systems 150 Gateway Connections 151 general problem determination 238 Instance Configuration 151 list of all 142 Login and Logoff 152 more information 141 Number Range 152 OS and LAN 152
R
R3_Monitor_ABAP_Dumps policy 165 R3_Monitor_Batch_Jobs policy 166 R3_Monitor_File_Systems policy 166 R3_Monitor_Production_Repairs policy 166 R3_Start_Buffer_Monitoring policy 166 R610_00xxx.ITM files 8, 25 R610_00xxxU.ITM 8 R610_00xxxU.ITM files 25 R610_DELETE files 8, 25 real-time data, viewing 27 recovering the operation of a resource 28 Refresh Database Statistics Results workspace 52 remote deployment Agent tab 14 command line 15 Tivoli Enterprise Portal 14 remote deployment problem determination 230 Remote Function Calls 16 remote function modules, removing 25 remote management 16 removing remote function modules from mySAP 25 reporting, CCMS 23 requirements disk space 6 memory 6 Monitoring Agent for mySAP 5 operating systems 5 other 6 Reset Gateway Statistics Results workspace 53 resource, recovering operation 28 Response Time situations 154 RFC See also Remote Function Calls connections 21
113
Index
255
situations (continued) Output 153 overview 141 predefined 142 Private Memory 154 Private Mode 154 Response Time 154 SAP Office 154 SAP Router 154 SAPGUI 154 Service Response 154 specific problem determination 237 Spool 156 System Log 156 Transactional RFC 157 Transport 157 Updates 157 values, modifying 30 Work Processes 158 SM37 transaction 9 special alerts generated by the agent 39 Spool Output workspace 54 Spool Requests attribute group 113 workspace 54 Spool situations 156 Start Job action 162 starting the Monitoring Agent for mySAP 13 STMS transaction 9 stopping the Monitoring Agent for mySAP 13 Sub-Application Performance workspace 55 subnodes :Grp 33 :Ins 33 :Sys 33 support about 241 contacting 242 describing problems 243 determining business impact of problems 243 gathering information for 217 information centers for 241 knowledge bases for 241 obtaining fixes 242 on Internet 241 submitting problems 244 weekly update option 242 system identifier 11 System Log attribute group 115 situations 156 workspace 55 System Log Detail workspace 55 System Log Details attribute group 116 system number 12 System Summary (agent level) workspace 56 (system level) workspace 56
T
tacmd addSystem command Take Action commands 28 Cancel Job 160 Close CCMS Alert 160 Delete Job 161 15
Take Action commands (continued) Execute brarchive 161 list of all 159 more information 159 Output Request 162 overview 159 predefined 159 problem determination 240 Start Job 162 tasks 17 user IDs 17 tasks for using the agent 27 text elements 24 time spans 34 timestamps, alerts 40 Tivoli Data Warehouse 2 Tivoli Enterprise Console See IBM Tivoli Enterprise Console Tivoli Enterprise Monitoring Server 2 Tivoli Enterprise Portal component 2 interface 1 problem determination 234 Tivoli software information center xi Tivoli technical training xii Topology Information attribute group 117 tp addtobuffer command 8, 9, 25 tp import command 8, 9, 25 trace logging examples 219 trace logs 218 directories 218 examples 221 tracing, components 222 trademarks 249 training, Tivoli technical xii Transaction Performance attribute group 117 workspace 56 Transactional RFC situations 157 workspace 57 Transactional RFC attribute group 120 transactions agent-provided 21 SA38 24 SM37 9 STMS 9 transport files 8 Transport Log attribute group 122 workspace 57 Transport Objects and Steps workspace 58 Transport Objects attribute group 122 transport request, ITMK610_00xxx.ITM 9 Transport Requests attribute group 123 workspace 58 Transport situations 157 Transport Steps attribute group 125 transports, mySAP 7 troubleshooting 217 typeface conventions xii
256
U
uninstallation log file 220 problems 228, 232 removing remote function modules 25 UNIX configuring the agent for 10 operating systems 5 starting the Monitoring Agent for mySAP 13 stopping the Monitoring Agent for mySAP 13 Updates Information attribute group 127 Updates situations 157 user defining 7 IDs basic agent monitoring 16 IBMMON_AGENT 16 purposes supported 16 SAPGUI, launching 17 Take Action commands 17 User ID 12 User Information attribute group 128 workspace 59 user interfaces options 3 User Performance workspace 59 User Transaction Performance workspace 60 using IBM Software Services for Tivoli 244 utilities agent 15 commands 205 encrypting a password 19 ksar3exe 18 ksar3nfy 18 ksar3pwd 19 running automated functions 18 sapshcut 20 sending SAP Office email 18
V
values, modifying situations 30 variables logon environment 18 notation xiii SAPPASSWORD 18 SAPTRACE 226 SAPUSER 18 verifying prerequisites for data collection 9 viewing data 31 real-time monitoring environment 27
W
Warehouse Proxy agent 2 Warehouse Summarization and Pruning agent 2 WAS levels supported 5 Web Application Server 5 weekly update support option 242 Windows agent installation problems 228 configuring the agent for 10 operating systems 5 starting the Monitoring Agent for mySAP 13
Windows (continued) stopping the Monitoring Agent for mySAP Work Processes attribute group 130 situations 158 workspace 60 workarounds 227 agents 232 remote deployment 230 situations 237 Take Action commands 240 Tivoli Enterprise Portal 234 workspaces 235 workspaces ABAP Dumps 36 Active Users 37 Alerts 38 Application Performance 41 Archive Monitor 41 Asynchronous Updates 42 Batch Data Create 42 Batch Data Create Log 42 Batch Job Log 43 Batch Jobs 43 Buffer Performance 44 Close Alert Results 45 Close All Alerts Results 45 Data Transfer Information 46 Database 45 Database Logs 46 Developer Traces 47 Disable Gateway Statistics Results 47 Enable Gateway Statistics 47 Enqueue Locks 48 event 28 File Systems 48 Gateway Statistics 48 Historical Database 49 Historical Operating System 49 Historical Service Response Time 49 Instance Configuration 49 Instance Summary 50 list of all 35 Logon Groups 50 Logon Information 50 Memory 51 more information 34 Number Range Buffer 51 Operating System and LAN 51 Output Requests 52 overview 33 predefined 35 problem determination 235 Refresh Database Statistics Results 52 Reset Gateway Statistics Results 53 SAP Office Inbox 53 SAProuter Log 53 Service Response Time 54 Spool Output 54 Spool Requests 54 Sub-Application Performance 55 System Log 55 System Log Detail 55 System Summary (agent level) 56 System Summary (system level) 56 Transaction Performance 56 Transactional RFC 57
13
Index
257
workspaces (continued) Transport Log 57 Transport Objects and Steps 58 Transport Requests 58 User Information 59 User Performance 59 User Transaction Performance 60 Work Processes 60
258
Printed in USA
SC32-9443-00

Main r3

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Main r3

Hochgeladen von

Copyright:

Verfügbare Formate

Tivoli Monitoring for Applications: mySAP Agent

Tivoli Monitoring for Applications: mySAP Agent

Chapter 3. How to use the Monitoring Agent for mySAP . . . . . . . . . . 27

Chapter 4. Workspaces reference . . . 33

Chapter 1. Overview of the Monitoring Agent for mySAP . . . . . . . . . . . 1

Chapter 2. Requirements and configuration for the monitoring agent . 5

Chapter 6. Situations reference . . . . 141

Chapter 5. Attributes reference . . . . 63

Chapter 7. Take Action commands reference . . . . . . . . . . . . . 159

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Chapter 8. Policies reference. . . . . 165

219 220 222 225 227

Appendix D. Accessibility . . . . . . 245

Appendix C. Problem determination

Appendix E. Notices . . . . . . . . 247

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Copyright IBM Corp. 2006

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

About this guide

Who should read this guide

What this guide contains

Copyright IBM Corp. 2006

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Accessing terminology online

Accessing publications online

About this guide

Tivoli technical training

Conventions used in this guide

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Operating system-dependent variables and paths

About this guide

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Chapter 1. Overview of the Monitoring Agent for mySAP

IBM Tivoli Monitoring overview

Features of Monitoring Agent for mySAP

Components of Monitoring Agent for mySAP

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

User interface options

Chapter 1. Overview of the Monitoring Agent for mySAP

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Chapter 2. Requirements and configuration for the monitoring agent

Requirements for the monitoring agent

SAP Basis and Web Application Server (WAS) levels supported

v 4.6C v 4.6D v 6.10 v 6.20 v 6.30 v 6.40

Copyright IBM Corp. 2006

v 50 MB RAM per agent instance

Basic installation and configuration of the Monitoring Agent for mySAP

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Installing to the mySAP system

Installing SAP transport and defining the user

Chapter 2. Requirements and configuration for the monitoring agent

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Where: SID Target mySAP system ID

Verifying the prerequisites for data collection

Chapter 2. Requirements and configuration for the monitoring agent

Installing to the IBM Tivoli Monitoring system

Configuring the Monitoring Agent for mySAP

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Chapter 2. Requirements and configuration for the monitoring agent

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide

Starting or stopping the Monitoring Agent for mySAP

IBM Tivoli Monitoring for Applications: mySAP Agent: Users Guide